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
I need to generate specific consul check scripts for each created node.
To do that, I have looped on the VMs count and pass them as vars to rendered templates.
It was working fine with terraform 0.6.16. To migrate in 7.2, I have transformed
data.template_file.check_connection_to_jboss #0: : invalid or unknown key: count
I cannot see in the documentation reference to supported meta-parameters for data sources.
I have found the same limitation with null_data_source.
So, I would assume that this affects any data source.
Steps to Reproduce
terraform plan
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 22, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Terraform Version
Terraform v0.7.2
Affected Resource(s)
Related to data sources implementation
error noticed with
Terraform Configuration Files
Expected Behavior
I need to generate specific consul check scripts for each created node.
To do that, I have looped on the VMs count and pass them as vars to rendered templates.
It was working fine with terraform 0.6.16. To migrate in 7.2, I have transformed
into
Actual Behavior
I got the message
I cannot see in the documentation reference to supported meta-parameters for data sources.
I have found the same limitation with null_data_source.
So, I would assume that this affects any data source.
Steps to Reproduce
terraform plan
The text was updated successfully, but these errors were encountered: