-
Notifications
You must be signed in to change notification settings - Fork 83
add rustc-perf-one to bastion allow list #742
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
Conversation
2141c3c
to
084782f
Compare
even without the IP change, there's this diff which I'm not sure it's safe to apply:
|
engine_version = "16.3" | ||
instance_class = "db.t4g.micro" | ||
engine_version = "16.8" | ||
instance_class = "db.m7g.large" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that @Mark-Simulacrum bumped the instance some time ago. Not sure about the Postgres version upgrade.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably the db is configured in a way that aws automatically updates to the latest version of postgres (minor version updates only)
applied complete. Hopefully there wasn't downtime:
|
confirmed with Jakub that there was some downtime. But at least now |
Merging this first to unblock the team. Then I also wrote #741 to avoid copy pasting the IPs, but for that one I need to ask a review.