Currently, when creating or updating an inventory source, the source_project parameter is limited to projects within the same organization. While selecting a source project from another organization is possible via the UI or API, it is not supported through the inventory_source module. This limitation restricts users from automating cross-organization workflows using this module and can lead to duplicated projects and increased maintenance overhead.

Proposed Enhancement:
Enable the ability to specify a project from a different organization as the source project for an inventory source. The system should:

• Validate the existence of the specified project across organizations.

• Assign the project as the source_project for the inventory source if found.

• Provide a clear error message if the project cannot be found.

Benefits:

• Supports cross-organization automation workflows.

• Reduces project duplication and simplifies maintenance.

• Increases flexibility for users managing multiple organizations.

Use Case:
A client is migrating all their organizations from Ansible Tower to AAP 2.4 through Code as Configuration (CaC). They have standardized projects that need to be used across multiple organizations. While the UI and API allow this, automating inventory source creation through ansible.controller collection is currently blocked. Enabling this feature in the module allows the client to maintain a single source of truth and fully automate their workflows.
Impact:

• Enhances functionality while remaining backward-compatible.

• Improves usability for multi-organization environments.

Tested On:

• AAP Version: 2.4

• ansible.controller Version: 4.2.25

PR in awx.awx collection: 

https://github.com/ansible/awx/pull/16146