This repository has been archived by the owner on Jan 12, 2022. It is now read-only.
chore: handle older controller config schema #594
Merged
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
Between V1 and V2 schemas there was a cluster launched that had the tenant_api_authenticator_pubkey_set_json field but before logRetention and metricRetention were renamed. Signed-off-by: Simão Reis <sreis@opstrace.com>
sreis
force-pushed
the
sreis/test-customer-upgrade
branch
from
166a347
to
2d8a190
Compare
Signed-off-by: Simão Reis <sreis@opstrace.com>
|
I also ran the upgrade test for this PR, and it came back green. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Between the use of ControllerConfig V1 and V2 schemas there was a cluster launched that had the tenant_api_authenticator_pubkey_set_json field but before logRetention and metricRetention were renamed.