Open dekimsey opened 4 years ago
Alternatively, it could be handled like the engine_version parameter in aws_db_instance where if auto_minor_version_upgrade is set, you can just provide a prefix of the version so "5.5" would work for all "5.5.x" versions.
This is still a problem. Can this be flagged as a bug? Currently auto_minor_version is not usable due to this problem
This bug still exist. Do we have any timeline about when is this gonna resolve?
This is still an issue as of June 2023
am i right that this has been fixed as of closing of https://github.com/hashicorp/terraform-provider-aws/issues/38930 ?
Community Note
Description
When using the
auto_minor_version_upgrade
, theengine_version
parameter can drift (become out of date). This causes spurious plans where terraform wants to downgrade the engine. I propose whenauto_minor_version_upgrade
is set, the engine version be compared as a glob on the minor version.Thus eliminating plan reports like such:
Perhaps instead, a new
minimum_engine_version
parameter should be set. Thus allowing AWS automatic upgrades to happen gracefully and not have terraform attempt to downgrade.New or Affected Resource(s)
Potential Terraform Configuration
Alternatively, re-interpret the existing parameter as a minimum if auto_minor_version_upgrade is set.
References
0000