Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Product not being associated with API after publishing #695

Open
JamesProant opened this issue Oct 22, 2024 · 1 comment
Open

[BUG] Product not being associated with API after publishing #695

JamesProant opened this issue Oct 22, 2024 · 1 comment

Comments

@JamesProant
Copy link

Release version

6.0.1

Describe the bug

When publishing an API (with the setting "publish-all-artifacts-in-repo") the product is not being associated with the API. The product itself is being published, but it is not being connected with the API. In previous APIOps versions this worked fine. Since upgrading to version 6.0.1 this has stopped working for us.

Artifacts:

Image

In the older version of the APIOps the extractor would associate the product with the api using the apis.json file (this is a screenshot from version v5.1.1 of APIOps):

Image

This worked as expected, the product was associated with the API and when publishing, the product was connected with the API in the portal.

Expected behavior

When running the publisher, the product should be associated with the API.

Actual behavior

No product is being associated with the API.

Reproduction Steps

Using APIOps v6.0.1
Extract API using extractor pipeline, with specific productName defined in extractor config file.
Publish API using publisher pipeline.

Copy link

  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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant