-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Always changes in aws_instance.vpc_security_group_ids
list
#2036
Comments
Duplicate of #2034 |
Hi everyone! Sorry you have been having trouble with this Due to the high volume of reports surrounding this, the maintainers will be looking into this sometime in the near future (including the already open PRs: #1911, #2338). There are some nuances around this configuration that make it harder than a quick fix and we certainly do not want to make the situation worse. We'll keep you updated. As a friendly reminder: voting with 👍 reactions on the original issue/PR comment is the best way to get our attention. |
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! |
This issue was originally opened by @ruudk as hashicorp/terraform#16434. It was migrated here as a result of the provider split. The original body of the issue is below.
Suddenly Terraform started to behave weird. All my
aws_instances
would give changes in thevpc_security_group_ids
list. But I didn't make any changes.It seems that Terraform thinks my instances don't have any security groups set-up, and thinks that it needs to add the ones in the configuration, while in fact, the servers already have those security groups set-up.
Terraform Version
Terraform v0.10.7
Terraform Configuration Files
Debug Output
Skipping for now because of sensitive data.
I checked the log and found that when it decribes the Runscope Radar AWS Instance the AWS API returns:
so it does see the changes from AWS. But it ignores them somehow.
Crash Output
No crash
Expected Behavior
No changes
Actual Behavior
Terraform will perform the following actions:
Steps to Reproduce
On every Plan it has the same changes, when I apply them, they succeed.
Important Factoids
Running on Atlas
The text was updated successfully, but these errors were encountered: