Skip to content
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

feat: support changing more settings in keycloak #3497

Merged
merged 4 commits into from
Aug 3, 2023

Conversation

shreddedbacon
Copy link
Member

Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated
  • PR title is ready for inclusion in changelog

This adds the ability to configure additional realm settings easily using json files, and also set the admin user email address which seems to be required for configuring email.

There does exist an existing way to apply realm settings using an envvar, but it is cumbersome. This new way allows helm to create a configmap to then volumemount to the required location and be consumed.

I've separated out the smtp configuration to its own step so that the email configuration can be provided separately to other realm settings easily, but they still use the same endpoint in the end.

@tobybellwood tobybellwood mentioned this pull request Aug 1, 2023
3 tasks
@shreddedbacon shreddedbacon marked this pull request as ready for review August 2, 2023 03:26
@tobybellwood tobybellwood force-pushed the keycloak-email-realm-settings branch from e2b2876 to d3ca33b Compare August 2, 2023 23:51
Copy link
Member

@tobybellwood tobybellwood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested working

@tobybellwood tobybellwood merged commit ad72236 into main Aug 3, 2023
@tobybellwood tobybellwood deleted the keycloak-email-realm-settings branch August 3, 2023 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants