Open dannosaur opened 3 years ago
Do they even look at this repo? I think not. I also want this feature :/
We consistently review these feature requests, but may not be able to incorporate each item into the roadmap. We would like to see comments on how these apply to the broader community as well.
@pprahlad In my case I want to downgrade from Postgres 14 to 12 because of this . I can't . I will have to remove the environment and create everything from scratch. (Note: I don't care if the DB is re-created and I lose the data)
Hi Can we have an update on when this is likely to be fixed please? Thanks.
We are facing the same issue as well. Any update on this issue? Thanks.
Community Note
Tell us about your request In light of the recent notices from RDS regarding the EOL of various older DB engine versions, it appears to be impossible to get Elastic Beanstalk to modify the RDS engine version to do the upgrades.
Is this request specific to an Elastic Beanstalk platform? No
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I'm trying to upgrade my RDS DB engine version via the EB console. However, when viewing the configuration for the DB instance, I can change the instance type, username/password, but not the engine version.
Are you currently working around this issue? I could change it outside of EB in the RDS console, but in past experience this causes EB to not want to modify the environment every again (especially if it can't sync the target DB instance to the current configuration).
Additional context This is probably an urgent thing, given the timelines specified for PG9.5 and MySQL5.6. Once those versions leave the RDS ecosystem for good, ANY attempt to change ANYTHING with the DB instance within Elastic Beanstalk is GOING to fail, simply because it'll try to sync the DB engine version in the EB configuration with the RDS instance, and when the current configured version is no longer available, those EB environments become useless.