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

Instrument to promote best practices of writing werf configurations #78

Open
1 task done
distorhead opened this issue Aug 30, 2022 · 0 comments
Open
1 task done

Comments

@distorhead
Copy link
Member

Before proceeding

  • I didn't find a similar issue

Problem

We need some linting instrument to check that your werf project configuration: werf.yaml and .helm/templates confirms with some known best practices.

Solution (if you have one)

  1. werf lint command which performs some checks based on some rules.
  2. Mechanics for updating linting rules, to receive updates for such rules, ability to lock for some version of rules, updatable living database of such rules.
  3. Ability to enable such linting by default in the converge-like commands.

Additional information

Older issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants