You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had an issue with revisions in APIOps when any revision other than first revision was set to current.
By making the folder api folder name suffixed with ;rev=n, we noticed publish is working even for first Revision (;rev=1)
This helped us to fix multiple revision issue by having clear segregation of revisions.
At the same time, the extractor is not suffixed for first revision. Is there a property that can be set to make ;rev=n suffixed for all api folder names.
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.
Release version
v6.0.1.1
Question Details
We had an issue with revisions in APIOps when any revision other than first revision was set to current.
By making the folder api folder name suffixed with ;rev=n, we noticed publish is working even for first Revision (;rev=1)
This helped us to fix multiple revision issue by having clear segregation of revisions.
At the same time, the extractor is not suffixed for first revision. Is there a property that can be set to make ;rev=n suffixed for all api folder names.
Expected behavior
api/echo-api;rev=1
api/echo-api;rev=2
api/echo-api;rev=3
Actual behavior
api/echo-api
api/echo-api;rev=2
api/echo-api;rev=3
or
api/echo-api;rev=1
api/echo-api
api/echo-api;rev=3
Reproduction Steps
Extract
The text was updated successfully, but these errors were encountered: