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

Review Ansible-Lint skipped rules #10

Open
kpouget opened this issue Aug 22, 2023 · 1 comment
Open

Review Ansible-Lint skipped rules #10

kpouget opened this issue Aug 22, 2023 · 1 comment

Comments

@kpouget
Copy link
Contributor

kpouget commented Aug 22, 2023

In this PR we updated the Ansible linter, but also introduce multiple "skipped" rules (to keep the CI green).

These skipped rules should be reviewed, and decided one by one if the rule should be enforced or skipped.

Rules that are skipped:

  - 'command-instead-of-module'
  - 'command-instead-of-shell'
  - 'deprecated-local-action'
  - 'key-order[task]'
  - 'jinja[spacing]'
  - 'no-free-form'
  - 'chema[meta]'
  - 'name[missing]'
  - 'var-naming[no-reserved]'
  - 'var-naming[no-role-prefix]'
  - 'var-naming[pattern]'
  - 'yaml[colons]'
  - 'yaml[commas]'
  - 'yaml[comments]'
  - 'yaml[empty-lines]'
  - 'yaml[indentation]'
  - 'yaml[key-duplicates]'
  - 'yaml[line-length]'
  - 'yaml[new-line-at-end-of-file]'
  - 'yaml[octal-values]'
  - 'yaml[trailing-spaces]'
  - 'yaml[truthy]'
  - 'name[template]'
  - 'name[casing]'
  - 'risky-file-permissions'
  - 'risky-shell-pipe'
  - 'ignore-errors'
  - 'no-changed-when'
  - 'fqcn'
  - 'args[module]'

rules that should be enforced, at first glance:


-    command-instead-of-shell
-    jinja[spacing]
-    yaml[new-line-at-end-of-file]
-    risky-shell-pip
-    name[missing]
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'name[missing]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
@ccamacho
Copy link
Collaborator

I think also running some bashate checks anywhere where bash/command is used will be useful

ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 25, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 27, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 28, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment
like `tox -e linters` instead of consuming the GH action.

Partially-solves: openshift-psap#10
kpouget added a commit that referenced this issue Aug 28, 2023
This commit resolves the following lint rules:

- 'key-order[task]'
- 'jinja[spacing]'
- 'name[missing]'
- 'yaml[new-line-at-end-of-file]'
- 'yaml[trailing-spaces]'
- 'risky-shell-pipe'
- 'args[module]'

Also removes the branch constraint to run
the Ansible lint checks from any fork. This
is useful because in each contributor's fork
when pushing specific named branches the checks
will be executed, a future improvement could be
to run all the lints checks from a single environment like `tox -e
linters` instead of consuming the GH action.

Partially-solves: #10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 29, 2023
This commit resolves the following lint rules:

- 'var-naming[no-reserved]'
- 'var-naming[no-role-prefix]'
- 'var-naming[pattern]'
- 'yaml[colons]'
- 'yaml[commas]'
- 'yaml[comments]'
- 'yaml[empty-lines]'
- 'yaml[indentation]'
- 'yaml[key-duplicates]'
- 'yaml[line-length]'
- 'yaml[octal-values]'
- 'name[template]'
- 'name[casing]'

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 29, 2023
This commit resolves the following lint rules:

- 'var-naming[no-reserved]'
- 'var-naming[no-role-prefix]'
- 'var-naming[pattern]'
- 'yaml[colons]'
- 'yaml[commas]'
- 'yaml[comments]'
- 'yaml[empty-lines]'
- 'yaml[indentation]'
- 'yaml[key-duplicates]'
- 'yaml[line-length]'
- 'yaml[octal-values]'
- 'name[template]'
- 'name[casing]'

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 29, 2023
This commit resolves the following lint rules:

- 'var-naming[no-reserved]'
- 'var-naming[no-role-prefix]'
- 'var-naming[pattern]'
- 'yaml[colons]'
- 'yaml[commas]'
- 'yaml[comments]'
- 'yaml[empty-lines]'
- 'yaml[indentation]'
- 'yaml[key-duplicates]'
- 'yaml[line-length]'
- 'yaml[octal-values]'
- 'name[template]'
- 'name[casing]'

Partially-solves: openshift-psap#10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 29, 2023
This commit resolves the following lint rules:

- 'var-naming[no-reserved]'
- 'var-naming[no-role-prefix]'
- 'var-naming[pattern]'
- 'yaml[colons]'
- 'yaml[commas]'
- 'yaml[comments]'
- 'yaml[empty-lines]'
- 'yaml[indentation]'
- 'yaml[key-duplicates]'
- 'yaml[line-length]'
- 'yaml[octal-values]'
- 'name[template]'
- 'name[casing]'

Partially-solves: openshift-psap#10
kpouget added a commit that referenced this issue Aug 29, 2023
This commit resolves the following lint rules:

- 'var-naming[no-reserved]'
- 'var-naming[no-role-prefix]'
- 'var-naming[pattern]'
- 'yaml[colons]'
- 'yaml[commas]'
- 'yaml[comments]'
- 'yaml[empty-lines]'
- 'yaml[indentation]'
- 'yaml[key-duplicates]'
- 'yaml[line-length]'
- 'yaml[octal-values]'
- 'name[template]'
- 'name[casing]'

Partially-solves: #10
ccamacho added a commit to ccamacho/topsail that referenced this issue Aug 29, 2023
This commit resolves the following lint rules:

- 'var-naming[no-reserved]'
- 'var-naming[no-role-prefix]'
- 'var-naming[pattern]'
- 'yaml[colons]'
- 'yaml[commas]'
- 'yaml[comments]'
- 'yaml[empty-lines]'
- 'yaml[indentation]'
- 'yaml[key-duplicates]'
- 'yaml[line-length]'
- 'yaml[octal-values]'
- 'name[template]'
- 'name[casing]'

Partially-solves: openshift-psap#10
kpouget added a commit that referenced this issue Aug 29, 2023
This commit resolves the following lint rules:

- 'yaml'
- 'yaml[truthy]'
- 'risky-file-permissions'
- 'no-changed-when'

It moves 'yaml' to 'yaml[indentation]' and 'yaml[line-length]' to avoid
skipping rules that are needed.

Adds an exclusion folder for the .github folder due to
ansible/ansible-lint#3645

Updates the toolbox repo 'generate_ansible_default_settings' option to
enforce the linting of the parameters and constants.

Partially solves: #10
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

No branches or pull requests

2 participants