guythetechie

@rstelcer - the error message seems to point to a missing policy fragment, not to named value issues. It fails when creating a policy on operation `dependecycheck` in API `echo-api`,...

@TechPrototyper - status code 422 (unprocessable entity) means that there's a problem with the request. It's typically not something that will be fixed by a retry. We've successfully tested ApiOps...

@rhenatas - please use the latest version instead of v5. Any bug fixes will be implemented in the newer versions only. As for your questions: 1. You can prevent the...

@automachina - thanks for raising this. Could be related to #643. The revision logic is more complicated than I'd like, unfortunately. Spent dozens of hours on it and working around...

This is not an ApiOps issue, unfortunately. Azure API Management treats different versions of an API as separate APIs. When you publish to QA, you should still be able to...

@dagraham7 - I would suggest excluding subscriptions completely from ApiOps. In your `configuration.extractor.yaml`, set `subscriptionNames: [ignore]`. This will prevent subscriptions from being extracted when the extractor runs. Note that if...

@dagraham7 - that's correct. Another scenario where subscriptions get deleted is when ApiOps creates a brand-new product. Here is the flow: - dev has `productA`, prod does not have `productA`....

@sandhya-techie - we've seen strange issues like this with ADO in the past (see #170). Can you paste the full output of the last step in your extractor pipeline? Your...