Skip to content
Ansible Lint

fix: yaml idents in loki and mimir docker compose files #217

Sign in to view logs

fix: yaml idents in loki and mimir docker compose files

fix: yaml idents in loki and mimir docker compose files #217

Triggered via push March 2, 2025 16:22
@alesharikalesharik
pushed ef70bb9
master
Status Failure
Total duration 39s
Artifacts –

ansible-lint.yaml

on: push
build
31s
build
Fit to window
Zoom out
Zoom in

Annotations

6 errors
syntax-check[specific]: roles/docker_registry_server/tasks/main.yaml#L35
couldn't resolve module/action 'community.general.htpasswd'. This often indicates a misspelling, missing collection, or incorrect module path.
syntax-check[specific]: roles/pam_limits/tasks/main.yaml#L2
couldn't resolve module/action 'ansible.builtin.pam_limits'. This often indicates a misspelling, missing collection, or incorrect module path.
syntax-check[specific]: roles/postgres/tasks/main.yaml#L107
couldn't resolve module/action 'community.postgresql.postgresql_user'. This often indicates a misspelling, missing collection, or incorrect module path.
syntax-check[specific]: roles/promtail/tasks/main.yaml#L38
couldn't resolve module/action 'community.crypto.openssl_privatekey'. This often indicates a misspelling, missing collection, or incorrect module path.
syntax-check[specific]: roles/sudo/tasks/main.yaml#L6
couldn't resolve module/action 'community.general.sudoers'. This often indicates a misspelling, missing collection, or incorrect module path.
syntax-check[specific]: roles/vmagent/tasks/main.yaml#L80
couldn't resolve module/action 'community.crypto.openssl_privatekey'. This often indicates a misspelling, missing collection, or incorrect module path.