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
If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.
* module.pizza.data.google_compute_instance.default[0]: At column 73, line 1: invalid index operation into non-indexable type: TypeString in: ${data.google_compute_region_instance_group.default.instances.*.instance[count.index]}
Panic Output
Expected Behavior
Data structures should be created, each representing an instance in the MIG.
Actual Behavior
The splat (*) operator seems to be ineffective and terraform plan breaks.
Steps to Reproduce
terraform apply
Important Factoids
This bug frustratingly prevents generating DNS records for MIGs. Several other tickets in this repository mention that this way is possible, while stating it's an antipattern. While I agree that it's an antipattern, it is sometimes needed and simply doesn't work.
I'm pretty sure this is a limitation of the splat operator, specifically with nested output-only fields (which is exactly what a data source is for) and would be an issue to bring up with Terraform core. However, I believe the official stance will probably be "use 0.12 which has a better splat". :/
We as providers sadly don't have control over how the splat operator works. I'm not sure if you could work around using something like the built-in element or lookup functions. We've typically pointed people to issues like hashicorp/terraform#17048 where people have tried to find alternatives.
@emilymye As terraform 0.12 isn't yet stable, that's not an option for me nor my clients. Thank you nonetheless, I'll continue following the issue you linked.
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 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Jun 16, 2019
Community Note
Terraform Version
Affected Resource(s)
data.google_compute_instance
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Data structures should be created, each representing an instance in the MIG.
Actual Behavior
The splat (
*
) operator seems to be ineffective andterraform plan
breaks.Steps to Reproduce
terraform apply
Important Factoids
This bug frustratingly prevents generating DNS records for MIGs. Several other tickets in this repository mention that this way is possible, while stating it's an antipattern. While I agree that it's an antipattern, it is sometimes needed and simply doesn't work.
References
The text was updated successfully, but these errors were encountered: