Fix export flow to detect thumbnail changes from the current API as opposed to the latest revision #12656
Conversation
This file contains 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
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.
Purpose
API thumbnail is not getting exported when the
--latesttag is used with the export command. However, this behavior is only noticed when the thumbnail uploading was done post-deployment. Thereby, the deployed API had no knowledge on the thumbnail update that was made to the current API.In order to resolve this issue, we have replaced the revisioned version with the current API state when it comes to the thumbnail extraction flow. The same applies to API products as well. This PR fixes the issue for both APIs and API Products.