-
Notifications
You must be signed in to change notification settings - Fork 52
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
PostgreSQL 11 is EOL and out of standard support for RDS causing additional cost #96
Comments
sure! would you like to submit a PR? |
I could I'm just not sure what we'd need to watch out for for CI / testing of this... ? If it's all automatic , I'm fine with a 1-3 liner for it that will change to the latest 11 (11.22) to 12.17 You can't just do 11 -> 12 .. needs to be 12.17 and we need to assume that people are on the latest minor for the upgrade to work without issue on aws's side (which is a resonable assumption I think given it upgrades minors automatically) You also need to add allow_major_version_upgrade = true Is that ok ? |
Actually I'm going to keep allow_major & apply to false and add that as a var for the user |
See: #97 |
I'm hitting this issue as well, in fact the terraform apply no longer works:
Is this repo still the recommended way to set up metaflow? |
The PostgreSQL version used in the datastore module is currently 11 as seen in :
terraform-aws-metaflow/modules/datastore/variables.tf
Line 14 in ee7093c
However this version is now at EOL and costs extra to be supported by AWS (0.10$/h/VCPU) see:
https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html
https://aws.amazon.com/rds/postgresql/pricing/
Could this be upgraded ?
The text was updated successfully, but these errors were encountered: