-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to new Portal domain name #272
Comments
* Scraped data2.umccr.org as initially planned * Related and start of dual domains support umccr/infrastructure#272
* Internally codename as `data2` client that would use the same Portal backend but with newer Portal v2 UI. * Client repo branch `v1-main` is still current PROD at data.umccr.org * Client repo branch `main` merges will pipe to portal.umccr.org * Also started of #272 and, together with v2 UI migration change management time window towards Q2/Q3 '23 eta
Update 09/12/2022 https://umccr.slack.com/archives/C025TLC7D/p1670580816232859 |
* Part of epic umccr/infrastructure#272
* DEV: https://portal.dev.umccr.org * STG: https://portal.stg.umccr.org * This is the phase 2 of switching portal to new domain. We still keep PROD domain; until later time, post Ocicat release. Related #272
Status Page UI updated Portal domain usage with PR umccr/data-portal-status-page#83 |
* This removes Portal now obsolete domain pattern throughout i.e. `[api.]data.[dev|stg|prod].umccr.org` * Along with detaching the associated SSL certificate from ACM * This will go multiple stages and this is the Phase 1 of umccr/infrastructure#272
* This removes the following exported system parameters: ``` /data_portal/backend/api_domain_name /data_portal/backend/certificate_arn ``` * At consumer side, these should be replaced new system parameter coordinate at: ``` /data_portal/backend/api_domain_name2 /data_portal/backend/certificate_arn2 ``` * This will go multiple stages and this is the Phase 1 of #272
We now totally removed DNS entries (first pass - soft deprecation) from Route53. Announced in Slack - https://umccr.slack.com/archives/C025TLC7D/p1721208827283479 In next Portal update, I will totally remove (old) Portal UI CodePipeline deployment from terraform / serverless. Schedule with |
Context:
data.umccr.org
toportal.umccr.org
Actions:
The text was updated successfully, but these errors were encountered: