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

Config schema validation #552

Closed
blancharda opened this issue Apr 4, 2024 · 0 comments · Fixed by #618
Closed

Config schema validation #552

blancharda opened this issue Apr 4, 2024 · 0 comments · Fixed by #618
Assignees
Labels
enhancement New feature or request

Comments

@blancharda
Copy link
Member

Overview

Currently there is no error output for unexpected config fields. It would be nice if there were a validation step that warned the user if a config was botched (yaml spacing, unexpected keys, schema misalignment etc).

For example, if a user forgets to add a variables key:

core:
  KEYCLOAK_CONFIG_IMAGE: nooooooope

Obviously no values would be passed to the core package.. but currently the deploy appears to continue to execute "successfully"

@blancharda blancharda added the enhancement New feature or request label Apr 4, 2024
@decleaver decleaver self-assigned this May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants