You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Terraform creates and ENI and it's attached out of band, Terraform
should not attempt to remove the attachment on subsequent runs.
fixes#2436fixes#2881
If Terraform creates an ENI and it's attached out of band, Terraform
should not attempt to remove the attachment on subsequent runs.
fixes#2436fixes#2881
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.
ghost
locked and limited conversation to collaborators
May 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am creating a solution for NAT in AWS that when a new member of a NAT autoscale group is created, it will attach itself to the network interface.
the code effectively works as follows:
The network interface is terraform managed:
On subsequent Terraform runs the attached instance is removed from the network interface and EIP as it was not part of the initial creation
This feels like a sledgehammer approach - is this intended?
The text was updated successfully, but these errors were encountered: