-
Notifications
You must be signed in to change notification settings - Fork 5k
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
update deprecated keycloak admin deprecated env variables: https://ww… #75279
base: main
Are you sure you want to change the base?
update deprecated keycloak admin deprecated env variables: https://ww… #75279
Conversation
…w.keycloak.org/docs/26.0.6/upgrading/#external-infinispan-in-a-single-site-setup Signed-off-by: Mathias Beaulieu-Duncan <[email protected]>
9f878fd
to
5033367
Compare
Hi @singatias, thank you for your contribution! The changes looks good to me with some suggestions, but we need to wait until Keycloak 25.x is removed from our catalog order in order to merge these changes. That is the reason why our CI pipeline fails, since those new variables are only supported on Keycloak 26.x. My request for this code review:
|
Update readme notables changes and envrionment variables Signed-off-by: Mathias Beaulieu-Duncan <[email protected]>
Signed-off-by: Mathias Beaulieu-Duncan <[email protected]>
Thank you for guiding me. Let me know if there is anything else :) |
Description of the change
Minor changes to change
KEYCLOAK_ADMIN
andKEYCLOAK_ADMIN_PASSWORD
environment and secret variables to update to the new valuesKC_BOOTSTRAP_ADMIN_USERNAME
,KC_BOOTSTRAP_ADMIN_PASSWORD
Benefits
remove the deprecation message and reduce the upcoming maintenance when the env variables are removed
Possible drawbacks
could be confusing for people who update the container and don't pay attention to the env variable changes
Applicable issues
none
Additional information
I noticed the deprecation messages on my new instance of Keycloak and decided to make the changes since they were minor
Related chart PR: bitnami/charts#30636