This repository has been archived by the owner on Mar 2, 2024. It is now read-only.
22Q2-2 🐛 Fix setup MFA breaking due to grafana client ssm parameter #1005
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
client
Motivation and Context
The ArgoCD user pool client secret uses a
/okctl/cluster name/component/client_secret
format, but the Grafana userpool client secret uses a
/okctl/cluster name/client-secret
format. Thisinconsistency breaks retrieving a random client secret from the parameter store.
How to prove the effect of this PR?
First, verify that the
setup-mfa
command runs successfully with only theArgoCD user pool client by:
integrations.kubePromStack
to false and runningokctl apply cluster
okctl setup-mfa
works as expected.Then verify that it breaks when ArgoCD user pool client is not available by:
integrations.argocd
to false, and runokctl apply cluster
.okctl setup-mfa
breaksAdditional info
Types of changes
Checklist: