No option to supply multiple source control credential

[simenon]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.
• I am NOT reporting a (potential) security vulnerability. (These should be emailed to [email protected] instead.)

Bug Summary

In our setup we are migrating from source control system A to source control system B. Where we struggle in this migration is that the main playbooks are being migrated to B, while all other supporting playbooks are remaining on system A. This create a situation where the playbook uses a requirements.yml where some point to A and some point to B. AWX can't handle this situation as you can only allow one source control credential, either for A or for B.

Ansible-galaxy will try to download the repositories in the requirements.yml but only has a credential for one of the repositories. So it will fail on this stage.

I think it is possible to differentiate source control credential based on the http link and pass these on to ansible galaxy. This implies that AWX would need to be able to attach multiple source control credentials to one project.

Note: it is possible to define one source control credential that connects over SSH and HTTPS, which technically makes the above situation possible, given the situation that A is accessed through SSH and B over HTTPS with user authentication or token based. I think this is a flaw in the source control credential system.

AWX version

23.9.0

Select the relevant components

• UI
• UI (tech preview)
• API
• Docs
• Collection
• CLI
• Other

Installation method

minikube

Modifications

no

Ansible version

No response

Operating system

No response

Web browser

No response

Steps to reproduce

See bug summary

Expected results

Ability to attach multiple source control credential to a project

Actual results

Only one source control credential can be attached to a project causing issues when there is a project with a requirements.yml that connects to more then one source control system

Additional information

No response