-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
205 deploy approval app #206
base: develop
Are you sure you want to change the base?
Conversation
- name: KEYCLOAK_USERNAME | ||
value: {{ .Values.approval.KEYCLOAK_USERNAME | quote }} | ||
- name: KEYCLOAK_PASSWORD | ||
{{- if .Values.approval.KEYCLOAK_PASSWORD }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let not put the direct insert of KEYCLOAK password in here, instead just make it only to use the secret like you put below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but I would need to overwrite it with production keycloak password on dev, hence I have this additional logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dev and prod uses different secret so you can set it in there, instead of directly put
Ready to be reviewed.
Since currently I'm deploying on incore-dev connecting with production keycloak, I allowed the overrride (in the values file) to point to production keycloak url and password. But the default should be where it is default if no overrride.