chore: couch db version upgrade guide and instrumentation#2204
Open
PeterBaker0 wants to merge 7 commits into
Open
chore: couch db version upgrade guide and instrumentation#2204PeterBaker0 wants to merge 7 commits into
PeterBaker0 wants to merge 7 commits into
Conversation
…rd name Signed-off-by: Peter Baker <peter.baker122@csiro.au>
Signed-off-by: Peter Baker <peter.baker122@csiro.au>
Signed-off-by: Peter Baker <peter.baker122@csiro.au>
E2E ✅ passed
After downloading and extracting the .zip file, open Updated for commit bd82efe |
Signed-off-by: Peter Baker <peter.baker122@csiro.au>
PeterBaker0
changed the title
Signed-off-by: Peter Baker <peter.baker122@csiro.au>
Signed-off-by: Peter Baker <peter.baker122@csiro.au>
stevecassidy
approved these changes
Jul 27, 2026
stevecassidy
left a comment
stevecassidy
left a comment
Contributor
There was a problem hiding this comment.
Looks ok with a few comments.
| @@ -0,0 +1,278 @@ | |||
| #!/usr/bin/env bash | |||
Contributor
There was a problem hiding this comment.
Can this be in the AWS folder please.
| @@ -0,0 +1,189 @@ | |||
| /* eslint-disable n/no-process-exit */ | |||
Contributor
There was a problem hiding this comment.
This facility would be useful but better as an API endpoint for SYSTEM_ADMIN so that we can easily access it on a given server. Maybe a separate PR.
| @@ -0,0 +1,77 @@ | |||
| { | |||
Contributor
There was a problem hiding this comment.
Was this supposed to be here?
| @@ -0,0 +1,198 @@ | |||
| # CouchDB version upgrade on AWS | |||
Contributor
There was a problem hiding this comment.
This is AWS specific but the 'migrate-with-keys' step after updating seems general, might be worth pointing that out near the top along with any other general issues.
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
2 participants
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
userDataCausesReplacement) and document the post-replace keys/migrate flow. NOTE this will force an instance replacement at deploy time even if you don't change the version.dump-user-emailsfor maintenance notices; haveenv-from-cdk-stack.shemitAWS_DEFAULT_REGION.Tested out on our stage replica. Works well. Note in the above that if you don't have the userDataCausesReplacement you don't get an EC2 replacement with a new user data run (to build the new couch version) but it does mean for current builds you'll get an instance replacement which is a bit risky if not coordinated well. Future ones won't experience that unless the user data hash changes (which it shouldn't typically).
Note if you don't detach the volume prior to running the instance replacement, you'll get a CFN error about the volume being already attached. Known CFN bug we have to work around.