Skip to content
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_network_interface_attachment: Add import functionality #26655

Closed
jpbuecken opened this issue Sep 5, 2022 · 2 comments · Fixed by #27364
Closed

aws_network_interface_attachment: Add import functionality #26655

jpbuecken opened this issue Sep 5, 2022 · 2 comments · Fixed by #27364
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service. service/vpc Issues and PRs that pertain to the vpc service.
Milestone

Comments

@jpbuecken
Copy link

jpbuecken commented Sep 5, 2022

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Please implement terraform import for aws_network_interface_attachment.

We cannot use the attachment block of aws_network_interface that support import already.
It does not support a detach (just deleting the attachment block does not result in changes)
We need to have more control about attaching and detaching of nics.
Use cases:

  • Migrate a nic from instance A to instance B.
  • Rebuild the instance from newer image, but keep all nics as it. Used for some upgrades.
  • Using aws_network_interface_attachment is similar to aws_volume_attachment, so the concept is known and similar concepts make code more understandable.

Since there is code to refresh the state file, a READ functionality is already in place. (at least for aws_network_interface)
And so I assume the import functionality is not too much to ask for it, isn't it?

New or Affected Resource(s)

  • aws_network_interface_attachment

Potential Terraform Configuration

resource "aws_instance" "instance" {
}
resource "aws_network_interface" "secondary_nic" {
}
resource "aws_network_interface_attachment" "secondary_nic" {
  instance_id          = aws_instance.instance.id
  network_interface_id = aws_network_interface.secondary_nic.id
  device_index         = 1
}

If someone want to import, maybe lookup the attachment_id in statefile from an already imported nic:

terraform import aws_network_interface_attachment.secondary_nic eni-attach-123456789

or maybe with a nic_id/instance_id combination:

terraform import aws_network_interface_attachment.secondary_nic eni-xxxxxxxxxxxxxx/i-xxxxxxxxxxxxxx

References

@jpbuecken jpbuecken added the enhancement Requests to existing resources that expand the functionality or scope. label Sep 5, 2022
@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/ec2 Issues and PRs that pertain to the ec2 service. service/vpc Issues and PRs that pertain to the vpc service. labels Sep 5, 2022
@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label Sep 6, 2022
@github-actions github-actions bot added this to the v4.37.0 milestone Oct 21, 2022
@github-actions
Copy link

This functionality has been released in v4.37.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service. service/vpc Issues and PRs that pertain to the vpc service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants