ansible-lint of all Ansible Playbooks for SAP · sap-linuxlab/ansible.playbooks_for_sap@bfb732f

Triggered via schedule July 29, 2024 10:28

main

Status Failure

Total duration 2m 8s

Artifacts –

ansible-lint.yml

on: schedule

10 errors and 2 warnings

yaml[comments]: ansible.playbooks_for_sap/.ansible-lint#L7

Missing starting space in comment

yaml[comments]: ansible.playbooks_for_sap/.ansible-lint#L8

Missing starting space in comment

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible-lint.yml#L34

Line too long (170 > 160 characters)

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible_software_availability.yml#L4

Line too long (183 > 160 characters)

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible_software_availability.yml#L48

Line too long (325 > 160 characters)

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible_software_availability.yml#L107

Line too long (161 > 160 characters)

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible_software_availability.yml#L161

Line too long (178 > 160 characters)

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible_software_availability.yml#L165

Line too long (170 > 160 characters)

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible_software_availability.yml#L170

Line too long (165 > 160 characters)

yaml[line-length]: ansible.playbooks_for_sap/.github/workflows/ansible_software_availability.yml#L172

Line too long (170 > 160 characters)

jinja[spacing]: ansible.playbooks_for_sap/deploy_scenarios/sap_bw4hana_standard_scaleout/ansible_playbook.yml#L432

Jinja2 spacing could be improved: {%- if sap_vm_provision_calculate_sap_hana_scaleout_standby > 0 -%}

jinja[spacing]: ansible.playbooks_for_sap/deploy_scenarios/sap_hana_scaleout/ansible_playbook.yml#L341

Jinja2 spacing could be improved: {%- if sap_vm_provision_calculate_sap_hana_scaleout_standby > 0 -%}