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.

Sign up for GitHub

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

Jump to bottom

Allow environment variables from existing secrets #822

Closed
Falcondevils opened this issue Dec 9, 2022 · 0 comments · Fixed by #1177
Closed

Allow environment variables from existing secrets #822

Falcondevils opened this issue Dec 9, 2022 · 0 comments · Fixed by #1177
Assignees
@AssahBismarkabah
Labels
enhancement

Comments

@Falcondevils
Copy link

Problem Statement

Current helm chart does not allow to use existing secrets for client secret or keycloak user password

Proposed Solution

The chart should allow existing k8 secrets to create environment variable so these variables can be referred in config files to be used as password/client secret etc

Environment

  • Keycloak Version: [e.g. 10.0.1]
  • keycloak-config-cli Version: [e.g. 1.4.0]
  • Java Version: [e.g. 11]

Additional information

No response

Acceptance Criteria

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AssahBismarkabah AssahBismarkabah

Labels
enhancement
Projects
os-competence-center-board
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

allow environment variables from existing secrets adorsys/keycloak-config-cli
2 participants
@Falcondevils @AssahBismarkabah