[BUG] Deleting objects in the git repository does not delete it from APIM
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the issue in release 6.0.1.7: remove an API or subscription from the Git repository, run the publisher pipeline, and inspect APIM. Trace the publisher pipeline's deletion handling and compare its behavior for APIs and subscriptions. Done means deleted repository objects are also removed from APIM without leaving the environment inconsistent.
Written by the indexing model from the issue text.
Description
Release version
6.0.1.7
Describe the bug
When deleting objects like API's or Subscriptions in the Git Repository, we removed the definitons from git repository. The expected behavior is for apiops to remove the objects from apim after running the publisher pipeline, but it does not remove and objects stay in apim
Expected behavior
The expected behavior is for apiops to remove the objects from apim after running the publisher pipeline,
Actual behavior
The objects continue to be on apim and no deletion happens, leaving environment in inconsistent state
Reproduction Steps
- Delete an API/Subscription in Git repository
- Run publisher pipeline
- Validate if the deletion happened, i see objects continue to be on apim after that
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·