demo-idp ci workflow #8
ci.yaml
on: push
Playbook linting
24s
Build and push container images for demo-idp playbook
0s
Annotations
10 errors and 1 warning
yaml[line-length]:
.github/workflows/ci.yaml#L37
Line too long (180 > 160 characters)
|
syntax-check[unknown-module]:
demo-idp/playbook.yml#L15
couldn't resolve module/action 'community.general.zypper'. This often indicates a misspelling, missing collection, or incorrect module path.
|
syntax-check[unknown-module]:
demo-idp/roles/keycloak/tasks/main.yml#L3
couldn't resolve module/action 'community.general.zypper'. This often indicates a misspelling, missing collection, or incorrect module path.
|
var-naming[no-role-prefix]:
demo-idp/roles/postgres/defaults/main.yml#L1
Variables names from within roles should use postgres_ as a prefix. (vars: keycloak_postgres_db)
|
var-naming[no-role-prefix]:
demo-idp/roles/postgres/defaults/main.yml#L2
Variables names from within roles should use postgres_ as a prefix. (vars: keycloak_postgres_user)
|
var-naming[no-role-prefix]:
demo-idp/roles/postgres/defaults/main.yml#L3
Variables names from within roles should use postgres_ as a prefix. (vars: install_postgres)
|
partial-become[task]:
demo-idp/roles/postgres/tasks/cleanup.yml#L3
``become_user`` should have a corresponding ``become`` at the play or task level.
|
partial-become[task]:
demo-idp/roles/postgres/tasks/cleanup.yml#L9
``become_user`` should have a corresponding ``become`` at the play or task level.
|
syntax-check[unknown-module]:
demo-idp/roles/postgres/tasks/main.yml#L3
couldn't resolve module/action 'community.general.zypper'. This often indicates a misspelling, missing collection, or incorrect module path.
|
partial-become[task]:
demo-idp/roles/postgres/tasks/main.yml#L26
``become_user`` should have a corresponding ``become`` at the play or task level.
|
Playbook linting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|