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
resource"digitalocean_floating_ip""auto_chess" {
droplet_id="${digitalocean_droplet.auto_chess.region}"# <-- Important: This field is intentionally wrong, should cause validation errorregion="${digitalocean_droplet.auto_chess.region}"
}
resource"digitalocean_domain""noahhuppert_com" {
name="noahhuppert.com"ip_address="${digitalocean_droplet.auto_chess.ipv4_address}"# Not important to issue, defined in other file
}
resource"digitalocean_record""auto_chess" {
domain="${digitalocean_domain.noahhuppert_com.name}"name="auto_chess"type="A"value="${digitalocean_floating_ip.auto_chess.ip_address}"
}
Terraform claims that digitalocean_floating_ip.auto_chess.ip_address is not found. This causes one to start debugging their code for a link/dependency error (Calling terraform graph, adding depends_on to everything, etc...). Instead of debugging their code for an incorrect digitalocean_floating_ip.auto_chess.droplet_id value.
Steps to Reproduce
Create a resource that is misconfigured
In the example above this is the digitalocean_floating_ip.auto_chess
The droplet_id parameter is intentionally set to be a digitalocean_droplet's region when it is supposed to be an id.
Create another resource that relies on a parameter of that resource
In the example above this is the digitialocean_record.auto_chess
It relies on digitalocean_floating_ip.auto_chess.ip_address
terraform plan
Receive a incorrect / not-really-showing-root-problem dependency error
Comment out the resource which is using the misconfigured resource
In the example above this would mean commenting out the digitalocean_record
Receive the correct validation error about your misconfigured resource
Important Factoids
Error messages and example code are in a module named auto-chess. Not included in the example code is a digitalocean_droplet named auto_chess, this is not important to the issue.
References
None
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 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.
ghost
locked and limited conversation to collaborators
Apr 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Affected Resource(s)
All? Found bug with:
digitalocean_floating_ip
digitalocean_record
I believe this is a Terraform core issue.
Terraform Configuration Files
Debug Output
Gist
Panic Output
None
Expected Behavior
Terraform should inform the user that the value they provided for
digitalocean_floating_ip.auto_chess.droplet_id
is incorrect like so:Actual Behavior
Terraform claims that
digitalocean_floating_ip.auto_chess.ip_address
is not found. This causes one to start debugging their code for a link/dependency error (Callingterraform graph
, addingdepends_on
to everything, etc...). Instead of debugging their code for an incorrectdigitalocean_floating_ip.auto_chess.droplet_id
value.Steps to Reproduce
digitalocean_floating_ip.auto_chess
droplet_id
parameter is intentionally set to be adigitalocean_droplet
's region when it is supposed to be an id.digitialocean_record.auto_chess
digitalocean_floating_ip.auto_chess.ip_address
terraform plan
digitalocean_record
Important Factoids
Error messages and example code are in a module named
auto-chess
. Not included in the example code is adigitalocean_droplet
namedauto_chess
, this is not important to the issue.References
None
The text was updated successfully, but these errors were encountered: