Ignore includeUIDInPath annotation when reviving db #835
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.
When
vertica.com/include-uid-in-path
is set totrue
, the operator will include the VerticaDB's UID in the path. The issue is that when reviving a db, we expect the path to an existing communal storage so that path should not be altered to avoid failure during revivedb. This PR adds a webhook rule that prevents setting the annotation totrue
when initPolicy isRevive