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
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 "me too" comments, 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
Terraform (and AzureRM Provider) Version
Terraform v0.11.10
provider.azurerm v1.19.0
Affected Resource(s)
data.azurerm_public_ip
Terraform Configuration Files
data"azurerm_public_ip""pubip" {
name="${var.name}"resource_group_name="${var.resource_group["name"]}"
}
output"instance" {
value={
id ="${data.azurerm_public_ip.pubip.id}"
name ="${data.azurerm_public_ip.pubip.name}"
fqdn ="${data.azurerm_public_ip.pubip.fqdn}"
domain_name ="${data.azurerm_public_ip.pubip.domain_name_label}"
ip_address ="${data.azurerm_public_ip.pubip.ip_address}"
}
}
Expected Behavior
Terraform apply will dump out the information on the public ip resource found in Azure.
Actual Behavior
If the public ip address is of type "dynamic" and is not associated with a network device the query will fail. Terraform plan will complain that the attributes fqdn, domain_name and ip_address are not known.
There is no way currently to check for the existence of the attributes in HCL to manage the output. There is no attribute to signal the status of a dynamically assigned public ip that can eventually used in a condition statement.
The text was updated successfully, but these errors were encountered:
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Mar 5, 2019
Community Note
Terraform (and AzureRM Provider) Version
Terraform v0.11.10
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Terraform apply will dump out the information on the public ip resource found in Azure.
Actual Behavior
If the public ip address is of type "dynamic" and is not associated with a network device the query will fail. Terraform plan will complain that the attributes fqdn, domain_name and ip_address are not known.
The Terraform state only has:
If on the other hand the "dynamic" ip address is assigned to a network device accordingly, it will properly display all the information.
The Terraform state shows:
There is no way currently to check for the existence of the attributes in HCL to manage the output. There is no attribute to signal the status of a dynamically assigned public ip that can eventually used in a condition statement.
The text was updated successfully, but these errors were encountered: