Repository navigation
Deploy staging, beta and releases to python.microbit.org's new buckets - #1371
Merged
Merged
Conversation
The buckets, distributions and roles are in microbit-foundation/microbit-org (apps/python). Releases still deploy under v/3/ and main under v/beta/, now in python.microbit.org's own bucket beside the versioner. main also deploys to stage-python.microbit.org under v/3/ for internal testing, so it builds twice, once per base path. Beta keeps behaving as staging (VITE_STAGE). Every stage deploys with an OIDC role rather than access keys. Only main and release tags can assume the role for staging, beta and production.
|
Preview build will be at |
Collaborator
Author
|
This scheme is intended to make it easy to drop in a beta branch build going to beta like CreateAI does. |
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.
Staging, beta and production move to private buckets behind CloudFront, defined in microbit-foundation/microbit-org's apps/python, as review did in #1369.
v/3/andmainunderv/beta/, now in python.microbit.org's own bucket beside the versioner.mainalso deploys to stage-python.microbit.org underv/3/for internal testing, so it builds twice, once per base path. Beta still builds withVITE_STAGE=STAGING, so it keeps today's simulator, analytics and flags.mainand release tags can assume the role for staging, beta and production; branches get the review role only.Merging starts the switch: the first
mainbuild fills the new staging/v/3and production/v/beta, and the old/v/betastops updating. The hosts still point at the old distributions until they're moved, which should follow soon after. The new production bucket already has the current release underv/3/.Both
mainbuilds upload Sentry source maps for the same release, which is worth watching.The
WEB_DEPLOY_AWS_*secrets go once the old distributions are cleaned up.