copying from the feature:

At the moment the only way to configure automation hub is to edit /etc/pulp/settings.py on the filesystem. This is:

• A terrible user experience: users should be able to easily see and update the most relevant settings to them
• Poorly documented: the settings.py file provides no context about what each setting does, nor comprehensive list what settings are available to customers.
• Dangerous: settings.py contains application secrets as well as other parameters that will completely break automation hub if they are updated incorrectly. Additionally the parameters that customers are expected to update have no validation and can easily get set to invalid values.

To fix this, we should create a settings API that allows customers to automate hub configurations and a UI that exposes all of the configuration options that users are expected to set.

SCOPE OF THIS EPIC:

for 2.4: focus on API, plus specific support needed for AAH-1027

post-2.4: follow on UI work/enhancements

Definition of Done (adjust as needed)

• CI is running, tests are automated and merged and successful
• DEV upstream code & tests merged
• DEV upstream documentation merged
• DEV downstream build attached to advisory
• QE - Test plans documented and attached to epic (or link to source)
• QE - automated tests merged and passing
• Docs - Downstream documentation is merged
• PM - all acceptance criteria are met (note: we want to start using the AC specific field)