[Enhancement]: provide import command when resource already exists

[Omarimcblack]

Description

When a resource already exists, introduce functionality that auto reports in the error message the correct way said resource can be imported. A read operation should therefore be performed when the EntityAlreadyExists error occurs. The resultant information can be used to populate import input.

- Error creating [resource-type] [resource-name]: EntityAlreadyExists: [resource-type] with [resource-name] already exists. status code: 409, request id:
+ Error creating [resource-type] [resource-name]: EntityAlreadyExists: [resource-type] with [resource-name] already exists. status code: 409, request id:...
+ import using $ terraform import [resource-type].[resource-name] [resource-id]

example:

terraform import aws_ec2_transit_gateway_peering_attachment.example tgw-attach-12345678

where the ID tgw-attach-12345678 would have been computed having tried to create an already present peering.

Affected Resource(s) and/or Data Source(s)

No response

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

No

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.