-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
aws_route_table bug with ignore_changes - "diffs didn't match during apply" #3869
Comments
|
I have the same issue. Only on initial run and destroy. |
Same here, |
This directive is a requirement for the way I'm provisioning a Kubernetes cluster with AWS cloud provider support. Kubernetes adjusts the route table at startup to suit its needs. Without |
Awesome - thanks phinze! Since original report I ended up going a different direction that didn't require ignore_changes. Will loop back if I encounter any more issues with it. |
…ticache_cluster-replication-group-id resource/aws_elasticache_cluster: Add replication_group_id argument
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
All output summarized here: https://gist.github.com/carlsverre/f50395eaee55952d95ed
Here is the repro (also in the gist):
If you comment the ignore_changes line it applies fine.
The text was updated successfully, but these errors were encountered: