Skip to content

[BUG] Noticed weird bug in v7.0.2/3 regarding extractor artifacts #863

Open
Open
[BUG] Noticed weird bug in v7.0.2/3 regarding extractor artifacts#863

Description

@nepsmaddy
nepsmaddy
opened on May 29, 2026

Release version

7.0.2/3

Describe the bug

In previous versions when we run the extractor with below config, extractor will only pick up the subscription(s) details assigned to the product name given in config.

Find the example extractor config used below. (before v7.0.1)

`diagnosticNames: [ignore]
loggerNames: [ignore]
policyFragmentNames: [ignore]

apiNames:

  • apiName1

backendNames:

  • backendName1
  • backendName2

namedValueNames:

  • namedValueName1
  • namedValueName2

productNames:

  • productName1
  • productName2

tagNames:

  • tagName1
  • tagName2
    `
    But in new version of extractor config if we do the same with new naming, extractor picking up every subscription(s) in the APIM instance with the product mention in the config.

This is causing issue for the publisher. if we run the publisher on the same, it will update all the subscription on new instance.

Expected behavior

When we have given product in extractor config, it should only pickup related subscription. Also along with this if we have given specific API in the extractor config the api should the only api in the artifacts.

Actual behavior

In this version, extractor pull all the APIs and Subscription attached with the product instead of the related ones like in previous versions.

Reproduction Steps

  1. Update the Version to 7.0.2
  2. create the configuration.extractor.yaml with the specific api and Product( Make sure mutiple api attached to the product to see the difference) (>=v7.0.1 )

`diagnostics: []
loggers: []
policyFragments: []
gateways: []
groups: []
versionSets: []
workspaces: []

apis:

  • apiName1

backends:

  • backendName1
  • backendName2

namedValues:

  • namedValueName1
  • namedValueName2

products:

  • productName1
  • productName2

tags:

  • tagName1
  • tagName2`
  1. Run the extractor and observe the artifacts.

You will see, all the subscriptions attached and all the APIs are attached in the product.

Activity

  1. github-actions commented on May 29, 2026

    @github-actions
    github-actionsbot
    on May 29, 2026 – with GitHub Actions
      Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

  2. nepsmaddy commented on May 29, 2026

    @nepsmaddy
    nepsmaddy
    on May 29, 2026
    ContributorAuthor

    Another issue i have noticed in this regarding tags. I provided tag for the single API. But extractor fetching all the APIs attached to the tag from DEV instance.

    Now when I am running publisher, it is failing stating the APIs are not available coz those are just in Dev right now. PFB error snapshot.

    Publisher failed. Please check the logs for more details. System.InvalidOperationException: Found at least one validation error: Resource 'tags/test/apis/common-core-prx' is missing its predecessor 'apis/common-core-prx'. Resource 'tags/test/apis/sample-proxy2' is missing its predecessor 'apis/sample-proxy2'.

  3. JProvAnt commented on Jun 11, 2026

    @JProvAnt
    James (JProvAnt)
    on Jun 11, 2026

    nepsmaddy Have you tried adding the subscription names to your config like in the configuration.extractor.yaml example?

    subscriptions:
  - subscriptionName1
  - subscriptionName2

  4. nepsmaddy commented on Jun 11, 2026

    @nepsmaddy
    nepsmaddy
    on Jun 11, 2026
    ContributorAuthor

    hi James (@JProvAnt) yes we are doing it right now. But as per the previous versions working, When we give Product, associated subscription(s) will be fetched automatically. We need to give subscriptions names only if we want specific subscription from that product.

    Coz of this change, all my previous branches approx. 450 APIs, start failing. Fetching whole instances subscription and pushing it to next instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions