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

Improved template linting/validation and CI-integration #844

Merged
merged 8 commits into from
Aug 14, 2018

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Aug 14, 2018

Added a test that can be run locally and with the CI, even before chartpress is used to build images and the chart.

tools/templates/lint-and-validate.yaml

  1. Helm template linting with helm lint
  2. Helm template verification with helm template
  3. Rendered output linting with yamllint
  4. Rendered output validation against the k8s API schema with kubeval

linting-and-validation-in-ci

@consideRatio consideRatio force-pushed the lint-and-validate-ci branch 4 times, most recently from aa00612 to 7490567 Compare August 14, 2018 21:05
Previously when chartpress generated output to values.yaml, it could
turn `"strings"` to `'strings'` and `null` to nothing.
When two sources of values, like the charts defaults in values.yaml and 
those provided by the user in config.yaml merged a dict from config.yaml 
with a field that was blank in values.yaml a warning was given. No more 
of that now.
@consideRatio consideRatio merged commit 55ef0a6 into jupyterhub:master Aug 14, 2018
@manics manics mentioned this pull request Aug 15, 2018
7 tasks
@choldgraf
Copy link
Member

Really nice! Is this something we could document in the devdocs somewhere?

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