Update the integrations build script to support the moving of a manifest v2 key #14175
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
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.
What does this PR do?
Update the integrations docs build to support the fact that
classifier_tagsis moving under thetilekeyThis maintains backwards compatibility while we migrate existing manifests, in that it looks for the new value first, then falls back on the existing location. Once all manifests are migrated, this should be updated to stop looking at the old path.
Motivation
The
classifier_tagskey was meant to go undertile, but an issue occurred that we're working to resolve :)Additional Notes
Reviewer checklist