Open jparnaudeau opened 2 years ago
Voting for Prioritization
Volunteering to Work on This Issue
Hi, @jparnaudeau have you tested this with a newer provider and core version, when I tested with my own resources I can confirm I see the Private IP address of my Nat Gateway in my output.
Hi @wzzzrd86 ,
backend_nategateways_ips = [
tostring(null),
tostring(null),
tostring(null),
]
backend_nategateways_ips = [
tostring(null),
tostring(null),
tostring(null),
]
Very strange.
I'll keep trying to reproduce, but here is my debug output, I'm trying to see if there is a difference between my Nat and your.
<natGatewayAddressSet>
<item>
<allocationId>eipalloc-0b56d6a5ecc036ba6</allocationId>
<associationId>eipassoc-0be264a31028997ee</associationId>
<isPrimary>true</isPrimary>
<networkInterfaceId>eni-05ddea11ed60b90fb</networkInterfaceId>
<privateIp>10.0.101.218</privateIp>
<publicIp>X.X.X.X</publicIp>
<status>succeeded</status>
</item>
</natGatewayAddressSet>
The issue if fixed. I am using Terraform v1.4.5 and I am able to retrieve the Private IP address of the NAT Gateway.
Terraform Core Version
1.2.9
AWS Provider Version
4.31.0
Affected Resource(s)
Expected Behavior
We should retrieve the IP address of the NAT Gateway. If i launch in DEBUG mode, i see that the IP address is correctly retrieved in the logs.
Actual Behavior
The provider returns null.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform init terraform apply --auto-approve
Outputs:
Debug Output
in the debug output, we see :
So the IP address is correctly retrieved by the api.
The complete log :
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No response