Open felipementel opened 2 weeks 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.
@felipementel - looks like the error is happening with a PUT, not a GET. Can you enable trace logging to get more details? It should show you the failing call as well as its payload.
@felipementel - looks like the error is happening with a PUT, not a GET. Can you enable trace logging to get more details? It should show you the failing call as well as its payload.
Maybe I found the problem!
The issue is, when searching for API information, not only the revision is being taken into account, but also the "apiRevisionDescription" field... so if it is different it is breaking.
Here are 2 points: perhaps remove the validation by the apiRevisionDescription field: including, if you want to change the description of the current revision OR change the error message to give a clearer view that the API exists but the description is different and needs to be adjusted.
Release version
v6.0.1.1
Describe the bug
Hello Team,
We are updating an existing API in APIM using APIOps. I am receiving the error below
So I took the URL and tried to make a call via Postman to actually check if the URL exists or not.
And the Http Request is OK!
Can you help solve this problem?