Description

With PULP_GALAXY_REQUIRE_CONTENT_APPROVAL=false set, after creating a repository, and matching distribution, uploading to that repository via the ansible-galaxy CLI, ultimately results in the collection existing in the "published" repo instead.

Key Dependency Versions

galaxy-importer==0.4.10
galaxy-ng==4.7.0
pulp-ansible==0.17.0
pulp-container==2.14.5
pulp-glue==0.19.0
pulpcore==3.23.3

Steps to Reproduce

1. Spin up galaxy_ng with PULP_GALAXY_REQUIRE_CONTENT_APPROVAL=false
2. Create a namespace
3. Create a repo (in my example "primary") and matching distro, no pipeline specified (None)
4. Configure a-g CLI via:

[galaxy]
server_list=primary

[galaxy_server.primary]
url=http://<host>/api/galaxy/content/primary/
username=admin
password=password

5. Publish via a-g CLI:

ansible-galaxy collection publish -s primary sivel-toiletwater-0.0.10.tar.gz -vvvvv

Actual Behavior

Collection appears in "published" and not in "primary" repo.

Expected Behavior

Collection should appear in "primary"

Additional info

As the "admin" user, when content approval is enabled, via PULP_GALAXY_REQUIRE_CONTENT_APPROVAL=true, no approval is required and the collection automatically shows up in "primary".

I have no idea what the expectation is for this "matrix", but it all feels a bit wrong to me.