Prepare release 3.1.0 · redhat-cop/cloud.aws_ops@06ce85d

Triggered via pull request January 27, 2025 16:45

abikouo

synchronize #150

Status Failure

Total duration 2m 11s

Artifacts –

linters.yml

on: pull_request

10 errors and 1 warning

Variables names from within roles should use aws_setup_credentials_ as a prefix. (vars: aws_security_token)

risky-file-permissions: .ansible/collections/ansible_collections/cloud/aws_ops/tests/integration/targets/test_deploy_flask_app/roles/run_deploy_flask_app/tasks/create.yaml#L147

File permissions unset or incorrect.

fqcn[canonical]: .ansible/collections/ansible_collections/cloud/aws_ops/tests/integration/targets/test_deploy_flask_app/roles/run_deploy_flask_app/tasks/delete.yaml#L33

You should use canonical module name `amazon.aws.elb_classic_lb_info` instead of `community.aws.elb_classic_lb_info`.

Variables names from within roles should use run_deploy_flask_app_ as a prefix. (vars: vpc_name)

Variables names from within roles should use run_deploy_flask_app_ as a prefix. (vars: vpc_cidr)

Variables names from within roles should use run_deploy_flask_app_ as a prefix. (vars: subnet_cidr)

Variables names from within roles should use run_deploy_flask_app_ as a prefix. (vars: resource_tags)

Variables names from within roles should use run_deploy_flask_app_ as a prefix. (vars: rds_subnet_group_name)

Variables names from within roles should use run_deploy_flask_app_ as a prefix. (vars: public_secgroup_name)

Variables names from within roles should use run_deploy_flask_app_ as a prefix. (vars: rds_secgroup_name)

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636