You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the infra.ah_configuration.repository role the execution fails with invalid arguments. It's saying ah_repositories is invalid but the documentation says that's what it should be. I did see
As per the changelog, there was a breaking change in v2.0.0 of this collection where the repository role was changed to accept ah_repositories as a list:
breaking_changes:
- Update collection repository roles to use allow for lists (you now need to
have a name for each repo and update the variable name) as this has been expanded
in the newer version of the product.
If you are using AAP2.4 it is recommended to begin using the collection_remote modules and roles instead.
That said, I will create a new issue to tidy up the arg_spec for the role, however the readme is already correct.
It also looks like you have a syntax error with your example as the variable should be under a vars option under the role.
Summary
When running the
infra.ah_configuration.repository
role the execution fails with invalid arguments. It's sayingah_repositories
is invalid but the documentation says that's what it should be. I did seegalaxy_collection/roles/repository/meta/argument_specs.yml
Line 3 in e5eb1e9
ah_repositories
.Issue Type
Ansible, Collection, Private Automation Hub details
OS / ENVIRONMENT
RHEL 8 with AAP 2.4
Desired Behavior
The playbook should execute the role correctly.
Actual Behavior
"msg": "Validation of arguments failed:\nah_repositories. Supported parameters include: ah_configuration_async_dir, ah_configuration_repository_secure_logging, ah_configuration_secure_logging, ah_host, ah_password, ah_path_prefix, ah_repository_certified, ah_repository_community, ah_request_timeout, ah_token, ah_username, ah_validate_certs, proxy_password, proxy_url, proxy_username.",
STEPS TO REPRODUCE
The text was updated successfully, but these errors were encountered: