Today for beta galaxy: Community Dev is deployed automatically from galaxy_ng and ansible-hub-ui master. Community Stage and Community Prod need manual steps to deploy.

Proposed Approach:

• Can be done now
  • Deploy Community Stage from master:HEAD, perhaps once nightly
  • Deploy Community Prod using same commit from Community Stage, perhaps 24hr after stage deploy
• Needs to be done prior to switchover
  • Gate the Community Prod deploy based on 2 test pipelines running against Community Stage: AAH-2178, AAH-2161
  • Gate the Community Prod deploy based on git diff between old and new commit, do not auto-deploy if there a change to `galaxy_ng/app/migrations/` or a y-stream change to `pulpcore`, `pulp_ansible`, or `pulp-container` in `setup.py` (which likely includes migrations). In this case the deploy requires downtime and/or read-replica process. This step can be relaxed depending on the work, adoption, and any automation of AAH-2196