Rds upgrade postgres for dev, stage and prod #378

rcgottlieb · 2024-09-17T20:08:38Z

Changes proposed in this pull request:

For any logging statements, is there any chance that they could be logging sensitive data?
Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the output, which can prevent unintentional leaks of sensitive data.

None

…rrectly

…gres testing

rcgottlieb added 13 commits September 6, 2024 13:45

upgrading dev db to postgres 16.1

7562466

updating staging db

e52fa56

indenting build manifest and removing env: so the manifest formats co…

7fa66dc

…rrectly

reverting changes to be added after build manifest PR

d6e71a5

changes to upgrade to Postgres16.1

1a76b6d

changing service var to be generic to allow for mysql, oracle or post…

64e173b

…gres testing

missed main smoke test script for updating to use the new var

d041377

missed one, added rds-service var to this test as well

bbbc8a4

fixed typos for service names

f203338

fixed more typos and missing parameters

c7225e3

wacamole round 4, rds-service var was missing

0f44a38

removed incorrect parameters to restaging

25479a5

Merge branch 'main' into rds-upgrade-postgres

eecd415

rcgottlieb requested a review from a team as a code owner September 17, 2024 20:08

markdboyd approved these changes Sep 17, 2024

View reviewed changes

rcgottlieb added this pull request to the merge queue Sep 17, 2024

Merged via the queue into main with commit a3d9efd Sep 17, 2024
1 check passed

rcgottlieb deleted the rds-upgrade-postgres branch September 17, 2024 20:10

rcgottlieb mentioned this pull request Sep 19, 2024

Platform RDS: aws-broker dev, stage, prod cloud-gov/product#3128

Closed

6 tasks