Terraform: null_resource does not have triggers attribute

Created on 26 Jun 2017  ยท  5Comments  ยท  Source: hashicorp/terraform

Terraform Version

Terraform v0.9.8

Terraform Configuration Files

apologies, but I can't share our full config at this time; I will try to either create a reproducible test case or vet the configuration so we can share it.

Debug Output

For the full terraform plan: https://gist.github.com/ahl/d7f895884600ce515fad9e133db92c29
For terraform plan -target=null_resource.svc-config: https://gist.github.com/ahl/a3b2e553043c2634b8a84dd7d805455b

Expected Behavior

I expected successful completion of the terraform plan

Actual Behavior

Error running plan: 2 error(s) occurred:

* aws_alb.svc-alb: 4 error(s) occurred:

* aws_alb.svc-alb[1]: Resource 'null_resource.svc-config' does not have attribute 'triggers.internal' for variable 'null_resource.svc-config.*.triggers.internal'
* aws_alb.svc-alb[2]: Resource 'null_resource.svc-config' does not have attribute 'triggers.internal' for variable 'null_resource.svc-config.*.triggers.internal'
* aws_alb.svc-alb[0]: Resource 'null_resource.svc-config' does not have attribute 'triggers.internal' for variable 'null_resource.svc-config.*.triggers.internal'
* aws_alb.svc-alb[3]: Resource 'null_resource.svc-config' does not have attribute 'triggers.internal' for variable 'null_resource.svc-config.*.triggers.internal'
* null_resource.svc-web: 1 error(s) occurred:

* null_resource.svc-web: Resource 'null_resource.svc-config' does not have attribute 'triggers.name' for variable 'null_resource.svc-config.*.triggers.name'

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform plan
bug config

Most helpful comment

I ran into this problem too. In my case, it was caused by some invalid condition inside of my trigger. I changed the logic inside the interpolation and this error went away.

All 5 comments

Note that I was able to apply my configuration by doing it with successive -target=... applies.

Hi @ahl! Sorry for this strange behavior.

Are you able to share the sequence of -target values you used to get this through? I'm curious to see what you had to eliminate from configuration to get this to work properly, since it seems from this error like some dependency edges were missed in the apply graph.

I ran into this problem too. In my case, it was caused by some invalid condition inside of my trigger. I changed the logic inside the interpolation and this error went away.

Hello! :robot:

This issue relates to an older version of Terraform that is no longer in active development, and because the area of Terraform it relates to has changed significantly since the issue was opened we suspect that the issue is either fixed or that the circumstances around it have changed enough that we'd need an updated issue report in order to reproduce and address it.

If you're still seeing this or a similar issue in the latest version of Terraform, please do feel free to open a new bug report! Please be sure to include all of the information requested in the template, even if it might seem redundant with the information already shared in _this_ issue, because the internal details relating to this problem are likely to be different in the current version of Terraform.

Thanks!

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.

Was this page helpful?
0 / 5 - 0 ratings