Promote updates-test → updates.simplerisk.com: mirror manifests on the prod channel#135
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Promotes
updates-test.simplerisk.com→updates.simplerisk.comso the S3 mirror workflow runs on the prod deploy branch, publishing the five XML manifests tos3://simplerisk-extras-533140816601/latest/updates/.Follow-on to #134 (which enabled this on the test channel — verified: the licensing service serves
releases.xmlfromtesting/updates/via theupdates-test.simplerisk.comhost).Commits in this promotion (1)
Mirror updates XML manifests to S3 for the licensing servicePrerequisites — already satisfied
licensing-prod): thesimplerisk-updates-publisher-prodrole exists and grantsPutObjectonlatest/updates/*.UPDATES_PUBLISHER_ROLE_ARN,AWS_REGION,EXTRAS_BUCKET).Effect on merge
The mirror workflow runs on the
updates.simplerisk.combranch → uploadsreleases.xml,Current_Version.xml,upgrade_path.xml,announcements.xml,extra_compatibility.xmltolatest/updates/.Verification after merge
curl -H 'Host: updates.simplerisk.com' https://<licensing-prod-alb>/releases.xmlstreams the XML (pre-DNS-cutover, via the prod ALB Host rule 427).Not included here
DNS cutover for
updates.simplerisk.com/updates-test.simplerisk.com→ the ALB is a separate, later step. Until then the ALB rules sit idle and only respond to explicitHost:headers.🤖 Generated with Claude Code