Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-1894

At prod switchover, keep old site available with old hostname

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

      Description:

      When we switch galaxy.ansible.com to point to the unified codebase site, keep the old site available under a different hostname like old-galaxy.ansible.com

      Also we should keep beta-galaxy.ansible.com pointing at the new site to maintain compatibility and deprecate / remove later.

      Proposed Solution:

      • add galaxy[-env].ansible.com routes, while also keeping the beta-galaxy[-env].ansible.com routes on the galaxy-ng deployments.
      • modify the routes on the old galaxy deployment to old-galaxy[-env].ansible.com.
      • add a 307 redirect in nginx for galaxy-ng from beta-galaxy.ansible.com to galaxy.ansible.com.
      • update PULP_CONTENT_ORIGIN envvar for galaxy-ng to new URLs.
      • update oauth apps with new URLs (for both old and new sites).
      • update monitoring dashboards with new URLs (for both old and new sites).
      • update lightspeed docs to remove "beta" from galaxy_ng URL.

              drodowic@redhat.com Daniel Rodowicz
              awcrosby5 Andrew Crosby (Inactive)
              Archiver:
              ranumula@redhat.com Raju Anumula

                Created:
                Updated:
                Resolved:
                Archived: