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
When making changes to specification.json the publisher does not publish the changes.
However, if you make changes to the corresponding apiInformation.json file (e.g. a bogus description change) the publisher pipeline will pickup the spec changes and publish these.
It seems without amending the api information, the pipeline does not recognise the changes on run.
Expected behavior
Publisher should attempt publishing the specification changes without the needing to amend the api information.
Actual behavior
As above.
Reproduction Steps
Make a change to just a specification.json file
Let publisher run
Publisher logs show no changes. Check APIM frontend editor in the Portal for the api to verify no changes present.
Repeat again but this time make a change to apiInformation.json file as well as the spec and it will publish.
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
Describe the bug
When making changes to
specification.json
the publisher does not publish the changes.However, if you make changes to the corresponding
apiInformation.json
file (e.g. a bogus description change) the publisher pipeline will pickup the spec changes and publish these.It seems without amending the api information, the pipeline does not recognise the changes on run.
Expected behavior
Publisher should attempt publishing the specification changes without the needing to amend the api information.
Actual behavior
As above.
Reproduction Steps
Repeat again but this time make a change to apiInformation.json file as well as the spec and it will publish.
Already briefly discussed with @guythetechie on #609
Logs attached.
publisher-log.txt
The text was updated successfully, but these errors were encountered: