-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
fix: Remove modified_at
from ignored changes on EKS addons
#2114
fix: Remove modified_at
from ignored changes on EKS addons
#2114
Conversation
### [18.24.1](v18.24.0...v18.24.1) (2022-06-19) ### Bug Fixes * Remove `modified_at` from ignored changes on EKS addons ([#2114](#2114)) ([5a5a32e](5a5a32e))
This PR is included in version 18.24.1 🎉 |
yep, the warning is gone now, and everything else seems to work fine as expected. thanks much! |
### [18.24.1](terraform-aws-modules/terraform-aws-eks@v18.24.0...v18.24.1) (2022-06-19) ### Bug Fixes * Remove `modified_at` from ignored changes on EKS addons ([terraform-aws-modules#2114](terraform-aws-modules#2114)) ([5a5a32e](terraform-aws-modules@5a5a32e))
### [18.24.1](terraform-aws-modules/terraform-aws-eks@v18.24.0...v18.24.1) (2022-06-19) ### Bug Fixes * Remove `modified_at` from ignored changes on EKS addons ([#2114](terraform-aws-modules/terraform-aws-eks#2114)) ([4f8dd86](terraform-aws-modules/terraform-aws-eks@4f8dd86))
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
modified_at
from ignored changes on EKS addonsMotivation and Context
complete
example using version 1.1.5 I am not seeing the changes in the plans as before. However, while forcing a minimum required version of 1.2.0 would be a breaking change, simply removing the ignored changes is not a breaking change. Either route (keep the ignored changes or remove) has the potential to show something in the plans/applies so why not remove it in favor of using the later versions of Terraform which doesn't incur a breaking change penaltyBreaking Changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request