Repository navigation
feat(krater): turn on krater production - #74
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
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.
Turns on Krater production:
enable = trueinhosts/weft/krater-production.nix. This is step 3 of the "Turn on production" checklist inhosts/weft/krater.nix.Merge this after #73. #73 has the first-build rev, the Slack channel ids and the production secrets, with
KRATER_WEAVE_CLIENT_SECRETset.The switch changes three hosts together:
kratermoves fromstagingOnlyAppstoapps, so skein creates thekraterrole and schema. The password comes fromcentral-prod-krater.age.krater-prod-*units, thekrater-prodnginx vhosts and thekrater-envsecret.krater-weftandkrater-storage-weftroutes, after thepatchwork-infrabump in jaspermayone/infra.tests/krater-weft.nixassumed that production was off. Its "by default" checks now compare against the switch file, and the "no production route" greps use an edge with the switch forced off. The test passes with either value of the switch.Rollout notes
krater-prod-webwaits for the database for 10 minutes, then fails.krater-prod-webis wanted bymulti-user.targetand requireskrater-prod-build. The first weft activation therefore runs the full image build, which takes several minutes. Run the deploy from a session that stays open.Checks
nixosConfigurations.weftandskeinevaluate.checks.x86_64-linux.krater-weftpasses every eval assertion and every grep up to the CI deploy command. The test passes with the switch on and off.grep ... krater-deploy: No such file or directory.mainfails the same way. The cause is the deploy script path from feat(krater): give ci a restricted deploy key for krater staging on weft #72, and this PR does not change it.