[server] Tie protected_secrets to ConfigCag #11765
Merged
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.
Description
This PR ties protected_secrets to a ConfigCat feature flag (on server) so that we can roll this out in production. This is the next step for #10134.
I've added the
protected_secrets
flag to ConfigCat and enabled it for non-prod environments.How to test
protected_secrets
flag, and that its secrets were fed from a Kubernetes secret.Release Notes
Werft options: