I’m not sure what we should do about this collection. On the one hand, it looks like there have been recent commits. On the other hand, there hasn’t been a new release since 2024. Additionally, there hasn’t been an answer to Validate compatibility with ansible-core 2.19.
There are tests, but I don’t see sanity tests… especially not with ansible-core 2.19 or later.
I tend to remove it from the Ansible Community Package. @SteeringCommittee What do you think?
I’m sorry, there is major doubt/drama in the community about the state of the awx project during the rearcitecting and now it is suggested to remove the collection of awx what is a (hopefully) active project that will ever have another tagged release.
It’s collection in the ansible organisation!
I would freeze any discussion on this until the steering committee/redhat gives a clear message on the state of awx.
I don’t believe Redhat would backtrack on the opensource commitment it gave, but discussions like this scare the living hell out of me.
I moved the above two posts to a new topic since the discussion of whether the awx.awx collection should be part of the Ansible community distribution is somewhat unrelated and (as the second post shows) potentially very confusing in the context of the orignal discussion (Edit: fixed link…).
@MalfuncEddie collections included in the Ansible community distribution have to satisfy certain rules. Removal from the community distrubtion is totally unrelated to availability of the collection on Ansible Galaxy or Automation Hub, and what plans Red Hat has with AWX.
Also the steering commitee has no say on AWX and anything AWX related, so the only ones who can say something on AWX are Red Hat. (Some individuals of the steering committee are RH employees and might or might not have more insight, or are part of the discussion; I’m only talking of the steering committee as a whole here.) The steering committee, on the other hand, is responsible for the Ansible community distribution.
The collection tests are running (Added Django and API requirements to AWX Contributor Docs for POC (#1… · ansible/awx@0d9483b · GitHub). The sanity tests seem to run with ansible-core 2.17, which is ancient, but the integration tests might (at least partially) run with the latest released ansible-core version (2.19.3) (I searched for core 2.1 in the integration tests output).
Considering our guidelines on removal of unmaintained collections that have not been declared as deprecated, I’m not sure awx.awx fits this category - at least yet.
Hi
Thanks for splitting this into a separate discussion thread.
I’m surprised that ansible-test sanity isn’t being run on the right versions of Ansible Core, thanks for raising that.
These seem to be very specific things that Red Hat can fix, so let me let the AWX (Controller) team know these need fixing.
Good point! I didn’t spot this since the CI is a bit confusing to me. Anyway, they should also start to test with ansible-core 2.20 in order to be prepared for Ansible 13.
For the record, I’m not against keeping this collection in the Ansible Community Package. The current situation just looks a little bit unclear to me and I wanted to ask around.
@MalfuncEddie As @felixfontein explained, this is not about killing the collection or something. It’s just about whether the collection still is compliant with the requirements to be kept in the Ansible Community Package. As I’ve said, the situation is a little bit unclear to me.
Currently the repo only tests against stable-2.17, I think that list needs updating to include 2.18. 2.19 & devel
For reference, this is what is currently failing against devel:
ERROR: Found 15 validate-modules issue(s) which need to be resolved:
ERROR: plugins/inventory/controller.py:0:0: invalid-documentation: DOCUMENTATION.options.aap_token.env.0.deprecated.Any('alternatives', 'alternative', msg=None): required key not provided @ data['options']['aap_token']['env'][0]['deprecated'][Any('alternatives', 'alternative', msg=None)]. Got None
ERROR: plugins/lookup/controller_api.py:0:0: invalid-documentation: DOCUMENTATION.options.aap_token.env.0.deprecated.Any('alternatives', 'alternative', msg=None): required key not provided @ data['options']['aap_token']['env'][0]['deprecated'][Any('alternatives', 'alternative', msg=None)]. Got None
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'credential_types' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'credentials' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'execution_environments' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'inventory' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'inventory_sources' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'job_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'notification_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'organizations' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'projects' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'schedules' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'teams' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'users' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
ERROR: plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'workflow_job_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
See documentation for help: https://docs.ansible.com/ansible-core/devel/dev_guide/testing/sanity/validate-modules.html
The AWX (Controller) team will get this fixed.