These additional scenarios include:

• view-only hub,
• hub with automatic approval of uploaded collections,
• High Availability Hub.

To add a scenario to the YOHO jenkins job, there are only a few files we need to edit:

In aap-qa (https://github.com/ansible/aap-qa):

• scripts/cloud_vars_from_env.py (the `cloud_image_vars` function needs to be modified to pick up any new relevant environment variables.)
• scripts/lib/common (need to add a new scenario to `setup_env_based_on_deployment_scenario.)

In aap-jenkins-shared-library (https://github.com/ansible/aap-jenkins-shared-library):

• vars/yoho.groovy (this is mostly just adding new parameters and making sure they are in the environment for the right steps.)

I [Henderson] don’t think we'll finish all of these (or maybe even any!) they are just some of the things we are working on and we can work on them when we have spare cycles. HA is the big complicated one, so almost certainly won’t happen (requires deployment of an HA database which isn't handled by the installer IIRC.)

People to talk to:

Henderson Hummel (me - I developed the YOHO job with a few other QEs last week and so the memories of adding a new scenario and debugging issues is fairly fresh in my mind )
Satoe Imaishi (primary developer of the AAP installer, will be a great contact when it comes to finding out what installer variables we need in order to install Hub in various configurations.)

This will be done when:
We have new options in the Jenkins YOHO job that toggle the following installation variables

• view-only hub (aka allows for anonymous browsing of collections, and potentially anonymous downloads (i.e. two parameters added to this job, and those params get passed to the installer.)
• automatic approval of uploaded collections.
• High Availability Hub (this is a nearly unreasonable stretch goal, but it's good to have something to reach for if we have lots of extra time.)