move-to-s2-b2-nad-cloud

[aprilrieger]

Update main.yml to deploy to Nadcloud using new s2/b2 domain naming convention

Pre-Deployment Note

Before running this deploy, the new domain(s) must be added to each existing Hyku tenant as additional allowed domains.
This ensures that tenants currently accessible via the old domains continue to function and can be accessed via the new s2/b2 domains once the deployment completes.

Story

Now that the client’s legacy AWS Hyku site has been decommissioned, we’re swapping the Nadcloud deployment domains from the previous s3/b3 naming convention to s2/b2. This ensures Nadcloud environments are deployed on the correct hostnames and receive TLS certificates automatically as part of the existing Ansible + certbot workflow.

Refs

• Adventist: scale down cluster #1034

What Changed

Updated main.yml to replace the legacy Nadcloud domains:

• s3.adventistdigitallibrary.org
• b3.adventistdigitallibrary.org

New deployments now use:

• s2.adventistdigitallibrary.org
• b2.adventistdigitallibrary.org

Domain changes are picked up by Ansible and used during certbot certificate issuance.

Expected Behavior Before Changes

Deployments reference the old Nadcloud domains:

• s3.adventistdigitallibrary.org
• b3.adventistdigitallibrary.org

TLS certificates (where present) are issued for the old hostnames.

Expected Behavior After Changes

Deployments reference the new Nadcloud domains:

• s2.adventistdigitallibrary.org
• b2.adventistdigitallibrary.org

On deployment, environments are created/updated using the new domains.

Certbot automatically issues/renews certificates for s2.adventistdigitallibrary.org and b2.adventistdigitallibrary.org as part of the Ansible deploy.

[maxkadel]

Thanks April!