-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Support ignoring whether or not an ENI is attached to an instance #2436
Labels
Comments
+1 : Ran into this as well |
👍 |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If we use Terraform to create an unattached
aws_network_interface
, and then have an ASG that launches instances that connect themselves to the ENI, future runs of Terraform will actually disconnect that network interface - it is imperative that we are able to ignore this difference and prevent Terraform from disconnecting the network interface on future runs.The text was updated successfully, but these errors were encountered: