search

Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
https://azure.github.io/apiops
MIT License
328 stars 193 forks source link

[BUG] Products not associating with Apis as using APIOps Toolkit for Azure APIM v6.0.1.1 latest version #652

Open username-anonymous opened 2 months ago

username-anonymous commented 2 months ago

Release version

APIOps Toolkit for Azure APIM v6.0.1.1

Describe the bug

I have to associate products with Apis in APIOps and using "APIOps Toolkit for Azure APIM v6.0.1.1" latest version hoping it contains fix of products association with apis. Product APIs are being stored in /artifacts/products/productName/apis/apiName/productApiInformation.json. After running publisher pipeline it's successful but products don't get associate with Apis.Can someone share the fix if this has been resolved and does v6.0.1.1 contain fix of issues and v6.0.1-rc1?

Expected behavior

Publisher pipeline is successful and products should associate with Apis on azure portal.

Actual behavior

Publisher pipeline is successful but products not associating with Apis on azure portal.

Reproduction Steps

Using latest APIOps Toolkit for Azure APIM v6.0.1.1

github-actions[bot] commented 2 months ago 
  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.
guythetechie commented 2 months ago

Can you post your publisher logs?

username-anonymous commented 2 months ago

I am looking into what level of publisher logs I can share here as it contains client data, meanwhile could you please confirm that does v6.0.1.1 contain fix of all previous products issues and v6.0.0-rc1 or I should use v6.0.0-rc1 source code to associate products with apis.

username-anonymous commented 2 months ago

Getting below error while running publisher pipeline for test as I mentioned earlier using latest APIOps toolkit v6.0.1.1, please provide the fix asap.

[error]System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/xxxx75-xxxx-xxxx/resourceGroups/rg-xxx-tst-xxx-xxx-api/providers/Microsoft.ApiManagement/service/apimxxxtstxxxx11/apis/apiName/diagnostics/applicationinsights?api-version=2023-09-01-preview failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"loggerId","message":"Logger Id 'apimxxxdevxxxx11-logs' does not exist"}]}}'.

guythetechie commented 2 months ago

@username-anonymous - see our Wiki for handling application insights loggers.

kantipenko commented 1 month ago

We have similar experience with publisher for the products. Here is screenshot, removed API and Products names: image