[BUG]Not able to remove gateways after removing it from the code.

Open
#839 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
azure, csharp
Domain
api, cloud

Research direction

Start by reproducing the issue in release v6.0.1.1 using the described artifacts → gateways → gateway name → apis path, first confirming that adding the gateway updates the APIM API collection. Trace the removal handling and verify that deleting the API reference causes the gateway to disappear from the APIM API collection.

Written by the indexing model from the issue text.

Description

Release version

v6.0.1.1

Describe the bug

In the api code, if we add the gateway, we are able to see the gateway in apim.
If we delete the gateway in api code, the gateway is not getting deleted.

Expected behavior

Under artifacts -> gateways -> gateway name -> apis -> yourapi --> Gateway is added in apim api collection..
Under artifacts -> gateways -> gateway name -> apis -> yourapi [remove this one] --> Gateway should be removed from apim api collection

Actual behavior

Under artifacts -> gateways -> gateway name -> apis -> yourapi --> Gateway is added in apim api collection.. [working as expected]
Under artifacts -> gateways -> gateway name -> apis -> yourapi [remove this one] --> Gateway is not getting removed from apim api collection

Reproduction Steps

Under artifacts -> gateways -> gateway name -> apis -> yourapi --> Gateway is added in apim api collection.. [working as expected]
Under artifacts -> gateways -> gateway name -> apis -> yourapi [remove this one] --> Gateway is not getting removed from apim api collection

Dominant language
C#
Stars
448
Forks
247
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.