-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Unable to ignore changes to RDS minor engine version #1198
Comments
Hey @joshuaspence, There is nothing Terraform can help on this specific topic: either you want AWS to upgrade your minor version and then you just need to update the This is based on your needs here :-/ Why not setting |
I think my main problem here is that I wasn't expecting it to happen (although I'll admit that I wasn't sure what my expectation was when using One way that Terraform could better handle this is to allow functions to be used in |
I'm more inclined to @Ninir here in the sense that Terraform kind of works as expected here (without context of the resource/field). You have specified That said it's a common enough problem (AFAIK) that it's worth thinking about solution.
Let me know what you think - and sorry for the re-labelling spam as I was thinking through the problem 🙈 |
I think that the solution that you proposed seems reasonable to me. |
Would it be possible to support defining the versions as Terraform would then pick the highest available version for the initial apply and after that it no longer matters as longs as the first or second digit don't change. I.e. one would have
|
Maybe this would be a good use case for a if d.HasChange("engine_version") && d.Get("auto_minor_version_upgrade").(bool) {
oldVersion, NewVersion := d.GetChange("engine_version")
if /* logic to correctly determine non-major version changes */ {
d.Clear("engine_version")
}
} |
This is now documented in the published docs, as per the pull request, but does not seem to work for me in aws-provider 1.46.0. I'm seeing the DEBUG statement from |
It's still there in 1.51:
|
@bflad was DiffSuppressFunc supposed to prevent this from occurring? I'm experiencing the same issue as @JohannesEbke with 1.59. If it was meant to be a |
https://www.terraform.io/docs/providers/aws/r/db_instance.html#engine_version
Looks like the problem doesn't exist anymore and the solution is documented. |
It still shows the difference. |
This issue should be fixed since the |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
We are using the
aws_db_instance
resource for managing RDS instances and I just came across an issue that arises from the use ofauto_minor_version_upgrade
. Basically, we have some Terraform configuration that looks like this:During one of our scheduled maintenance windows, Amazon have kindly upgrade this RDS instance from MySQL 5.7.10 to 5.7.17 (which is expected due to
auto_minor_version_upgrade
). As such,terraform plan
now shows the following change to be applied:I can workaround this by adding
engine_version
toignore_changes
, but doing so would prevent me from updating the major engine version. Ideally, I would be able to ignore changes only to the minor/patch version.The text was updated successfully, but these errors were encountered: