Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Publisher does not pickup changes to specification.json #634

Closed
riosengineer opened this issue Aug 14, 2024 · 2 comments
Closed

[BUG] Publisher does not pickup changes to specification.json #634

riosengineer opened this issue Aug 14, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@riosengineer
Copy link

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

  1. Make a change to just a specification.json file
  2. Let publisher run
  3. 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.

Already briefly discussed with @guythetechie on #609

Logs attached.
publisher-log.txt
image

Copy link

  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 guythetechie moved this to 🏗 In progress in APIOPS Roadmap Aug 14, 2024
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in APIOPS Roadmap Aug 14, 2024
@waelkdouh
Copy link
Contributor

Can you please take a look at other issues (open and closed) that touched on this topic.

@waelkdouh waelkdouh added the question Further information is requested label Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: Done
Development

No branches or pull requests

3 participants