-
Notifications
You must be signed in to change notification settings - Fork 62
Linting #23
Comments
We already have linting for scripts using shellcheck. Shellcheck dependency is also managed by Bazel, so no need to manually manage its version on each developer environment. |
Maybe use https://github.com/adrienverge/yamllint ? |
An example of using yamllint and shellcheck, skipping some folders, and in posix standard: |
Progress in add-yaml-linting branch. |
The linting script with yamllint is in place, but I'm having trouble installing yamllint with bazel. I have tried with https://github.com/bazelbuild/rules_python and things in the shape of the following, and a requirements.txt with yamllint, with no luck so far: (in WORKSPACE)
|
Right now the viccuad/add-yaml-linting branch contains a solution that: Adds bazel target Bazel's pip_install() is refusing to install pip, so for testing I have a workaround commit that installs pip as a system package in the gitlab image. To test:
TODO: |
One implementation of yaml linting (sans helm templates) at #161 |
Sources should be linted
helm lint
The text was updated successfully, but these errors were encountered: