Closed saiprasad-dhumal-ms closed 5 months ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @saiprasad-dhumal-ms š Thank you for taking the time to raise this! I notice that you're using a fairly old version of the Terraform AWS Provider. I also noted that private_ip
doesn't appear to be a valid argument for the aws_network_interface
resource.
Can you test with a more recent version of the provider and, if possible, supply debug logs (redacted as needed)?
Since we haven't heard back, I'm going to close this issue. If you're still having trouble, please feel free to open a new issue, referencing this one for context as needed.
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.
Terraform Core Version
1.6.6
AWS Provider Version
3.65.0
Affected Resource(s)
aws network interface: when we specify the private_ip address of network interface while creating, terraform plan will show it correctly but after terraform apply, assigned primary private IP address is different. Note that we already checked given IP is available in VPC.
Expected Behavior
Provided primary private IP should be the we specify in argument private_ip
Actual Behavior
Provided primary private IP is different than be the one we specified in argument private_ip
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Run below code:
pass appropriate arguments.
Debug Output
Panic Output
After we verify on console, found that private_ip is different
Important Factoids
No response
References
No response
Would you like to implement a fix?
None