CI #107
ci.yml
on: schedule
Matrix: ci / linter
Matrix: ci / molecule
Matrix: ci / sanity
Annotations
23 warnings
ci / linter (3.11, 2.15)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4, actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
meta-runtime[unsupported-version]:
meta/runtime.yml#L1
'requires_ansible' key must refer to a currently supported version such as: >=2.14.0, >=2.15.0, >=2.16.0
|
fqcn[keyword]:
playbooks/playbook.yml#L2
Avoid `collections` keyword by using FQCN for all plugins, modules, roles and playbooks.
|
fqcn[keyword]:
playbooks/validate.yml#L2
Avoid `collections` keyword by using FQCN for all plugins, modules, roles and playbooks.
|
var-naming[no-role-prefix]:
roles/wildfly_driver/defaults/main.yml#L2
Variables names from within roles should use wildfly_driver_ as a prefix. (vars: wildfly_user)
|
var-naming[no-role-prefix]:
roles/wildfly_driver/defaults/main.yml#L3
Variables names from within roles should use wildfly_driver_ as a prefix. (vars: wildfly_group)
|
var-naming[no-role-prefix]:
roles/wildfly_driver/defaults/main.yml#L4
Variables names from within roles should use wildfly_driver_ as a prefix. (vars: wildfly_version)
|
var-naming[no-role-prefix]:
roles/wildfly_driver/defaults/main.yml#L5
Variables names from within roles should use wildfly_driver_ as a prefix. (vars: wildfly_home)
|
schema[meta]:
roles/wildfly_driver/meta/main.yml#L1
$.galaxy_info.platforms[0].versions[0] 8 is not one of ['6.1', '7.1', '7.2', 'all']. See https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html#using-role-dependencies
|
name[template]:
roles/wildfly_driver/tasks/main.yml#L12
Jinja templates should only be at the end of 'name'
|
var-naming[no-role-prefix]:
roles/wildfly_driver/vars/main.yml#L2
Variables names from within roles should use wildfly_driver_ as a prefix. (vars: wildfly_driver)
|
ci / sanity (3.11, devel)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / sanity (3.11, stable-2.14)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / sanity (3.8, stable-2.9)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / sanity (3.11, milestone)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.15, prospero)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.14, prospero)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.15, default)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.15, install_options)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.15, yaml_config_validation)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.14, install_options)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.14, yaml_config_validation)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ci / molecule (3.11, 2.14, default)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|