-
Notifications
You must be signed in to change notification settings - Fork 14
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
Database Engine Version Upgrade #1486
Open
7 of 12 tasks
Comments
@kkrug Just a reminder that this upgrade needs to be completed in January. |
11 tasks
kkrug
added a commit
that referenced
this issue
Feb 3, 2025
kkrug
added a commit
that referenced
this issue
Feb 3, 2025
Merged
Merged
Merged
Merged
Merged
Merged
Merged
@r-bartlett-gsa @TCKapGrp I put this in testing if you wanted to do any quick regression testing to make sure the new DB are good |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a challenge.gov stakeholder, in order to ensure minimum downtime and proper testing of the challenge.gov application after upgrade, I would like the upgrade done by challenge.gov team (rather than by cloud.gov).
Acceptance criteria:
manage-rds export <instance-name>
manage-rds import <new-instance-name>
Switch Production Databases:After successful testing, finalize the data migration and promote the new database instance as the primary databasefor applications.manage-rds delete <old-instance-name>
For additional information, see https://docs.google.com/document/d/10HZ3opqdeYveKllbCciN6Jhdwf5Qs3NGaxOkY9EHJZQ/edit?usp=drive_link
#1438
The text was updated successfully, but these errors were encountered: