Warn, don't fail, when an API is not found when publishing an API product #756
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Warn, don't fail, when an API is not found when publishing an API product
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scenario:
ApiOps is used in a MultiRepo setup (~multiple independant teams)
API Products are managed & published in the central team repo
APIs are managed by the teams
When an API product is published to a higher environment, where the API itself does not exists yet, the deployment of the API Product fails the publish process.
PR Changes:
Catch the "API Not Found" exception when publishing an API Product and log a warning instead of throwing an exception.
This PR is the V6 version of #531