Closed jonathanyongyk closed 2 months 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.
Please post the logs here (make sure you scrub). Sounds like the git is not picking any changes.
@waelkdouh , i managed to resolve the issue from the hint you mentioned. i have a couple of other commits not related to APIM so git it is not picking up any changes from the latest commit. instead i need to choose to publish all the artifacts in the repo. Thanks.
Keep in mind it's usually better to allow the publish to pick the commit, which has the changes only on otherwise you are publishing everything which is more resource intensive process not to mention that it takes longer. Of course, there are situations where you republish everything if you see fit.
Release version
v5.1.4
Question Details
The publisher pipeline run successfully, but when i check the APIM instance, the changes is not actually deployed.
Expected behavior
API artifacts extracted from the "lower" environment (aka Dev) should be deployed to the "higher" environment (aka Prod). After running the publisher pipeline, both Dev and Prod APIM instance should be the same.
Actual behavior
Changes not deployed to Prod APIM instance despite the publisher pipeline run successfully.
Reproduction Steps
Run extractor pipeline to extract APIM settings from "Dev" environment. Merge pull request into main/master branch. Run publisher pipeline to publish to "Prod" APIM instance. (publisher pipeline run successfully, but changes not deployed)