-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
non-idempotent ec2 module #10
Comments
I am not seeing the same error but terraform wants to create a replacement instance for an instance created with this module. No changes made, just running plan and apply again. |
I am seeing what @jn9999 sees: a create/destroy loop. :/ |
Sorry for the delay in my response. From what I see there are at least 4 different arguments which can make this module non-idempotent, which is bad:
The problem with
Proposed solution:
These changes should make this module idempotent. Objections? Comments? PS: It helps to upvote related issues to increase chances of them being prioritized and fixed. |
The proposed solution sounds good to me since I already set the |
v1.1.0 has been released. |
…everal arguments (fixes terraform-aws-modules#10)
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. |
Hi,
I deploy ec2 instance using terraform-aws-ec2-instance module. After that I run one more time terraform apply without changing any resources in code and this leads to destroying my ec2 instance and execution errors.
terraform version
terraform code
zabbix_ex_v3.zip
The text was updated successfully, but these errors were encountered: