What is the nature and description of the request?
Migrating from AAP 2.4 -> AAP 2.5 includes a move of the Organization resource to gateway from controller. The previously used ansible.controller.organization module has parameters for configuring Galaxy Credential(s), the default Execution Environment, etc. These items can still be configured in the Gateway UI, but cannot be included as parameters to the module.
Why does the customer need this? (List the business requirements here)
To have a centralized RBAC experience, resources like an Organization should be able to be configured with a single configuration-as-code module.
How would you like to achieve this? (List the functional requirements here)
The gateway API should accept all parameters pertaining to the Organization resource and propogate configuration to backend APIs as needed. Otherwise, the customer is required to implement the additional requests using multiple configuration-as-code modules for the same resource.
List any affected known dependencies: Doc, UI etc..
The certified collections ansible.platform and ansible.control as well as the related validated content for configuration-as-code (infra.* collections).
Feature Request
Major