[BUG]Duplicate subscriptions created when publishing to multiple environments
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the extractor pipeline and publisher pipeline flow described for subscriptions/ artifacts across Dev and Test. Compare how subscriptions with the same displayName and scope are handled in the target environment. Done should be defined as preventing duplicate logical subscriptions, or excluding them by default if that is the chosen behavior.
Written by the indexing model from the issue text.
Description
Release version
v6.0.1.7
Describe the bug
When using the APIOps publisher to deploy APIs across multiple environments (e.g., Dev → Test → Prod), subscriptions included in the Git repository result in duplicate subscriptions being created in each environment, even if the displayName and scope are the same.
Expected behavior
Subscriptions with the same displayName and scope should be treated as the same logical entity and not duplicated in other environments.
Alternatively, subscriptions could be considered runtime-only data and excluded entirely by default, unless explicitly managed.
Actual behavior
Publishing creates duplicate subscriptions with the same display name but separate keys and internal IDs, leading to confusion and clutter across environments.
Reproduction Steps
- Extract from Dev APIM instance using the extractor pipeline — this includes subscriptions/ artifacts.
- Commit the extracted subscriptions into the APIOps Git repo.
- Run the publisher pipeline against a different environment (e.g., Test).
- Observe that new subscriptions with identical displayName are created in Test, instead of reusing or matching existing ones.
- 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 3/5 1-2 days Newbie friendliness 70/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
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RayWangQvQ/BiliBiliToolPro#1137 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100