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

Restructure the code as configurator + validator #3

Open
mjuric opened this issue Nov 26, 2019 · 0 comments
Open

Restructure the code as configurator + validator #3

mjuric opened this issue Nov 26, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@mjuric
Copy link
Member

mjuric commented Nov 26, 2019

The current ./configure script (unnecessarily) mixes two things:

  • Generating the Helm/shell configuration
  • Validating and describing it in human-readable terms (e.g., printing out a summary of what will be created, together with the cost, checking that Docker images exist, etc.)

These two should be split up (e.g. ./configure and ./validate), where ./validate would work from generated files. This would allow validation to be run on any Helm values.yaml setup, or even be run after the ./configure output has been heavily customized by the user.

This would probably require rewriting the validation stage in Python (for proper reading of YAMLs).

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

No branches or pull requests

1 participant