When I set this up originally, it create the Aurora cluster with the defined version. It appears that AWS has upgraded it in the background. Since I'm calling this as a module, I can't use lifecycle to ignore the change and move. This will likely prevent any future deploys.
Untested (I might tomorrow) but engine_version supports partials, which should allow AWS to do the forced upgrades without breaking things.
When I set this up originally, it create the Aurora cluster with the defined version. It appears that AWS has upgraded it in the background. Since I'm calling this as a module, I can't use
lifecycle
to ignore the change and move. This will likely prevent any future deploys.Untested (I might tomorrow) but
engine_version
supports partials, which should allow AWS to do the forced upgrades without breaking things.https://github.com/TechToSpeech/terraform-aws-serverless-static-wordpress/blob/abc903d9d3aabbb2fbb51e47679c0b2c61b3f6e7/rds.tf#L47