5 ms·
For a 2020 piece, two things seem outdated: > And you can’t even use the for_each trick with module imports. It just isn’t supported. Works since Terraform 0.
by kubanczyk 6y ago
For a 2020 piece, two things seem outdated:
> And you can’t even use the for_each trick with module imports. It just isn’t supported.
Works since Terraform 0.13 (released in August 2020).
> data "provider_thingy" "my_name_for_this_data"
> Though, like, why the quotes around the provider thingy?
Since 0.12 you can just write
data provider_thingy my_data {}
resource provider_thingy my_resource {}
They seem to keep the quotes for compatibility with v0.11. Yes, they should have updated the intro/examples to the simpler format.
> Required vs optional parameters are not very clearly called out and are not at all segregated.
Yes, in AWS provider. Other providers format the docs better and clearly segregate the required from the optional.
- igetspam 6y agoIf you've been using TF for any amount of time though, 0.13 is a breaking change (because semver... oh wait...). The migration from 0.11 to 0.12 was a PITA and if you're using any third party modules or resources, they still don't have consistent support for 0.13. Usung 0.12 currently gives you the most consistent experience. This is not bashing TF, it's just reality. I wish I had time to update everything to 0.13. The third party provider support alone makes it valuable.
- kubanczyk 6y agoI read you - I'm currently still going through 0.13 upgrade. The pain however is considerably smaller than 0.12 upgrade and I've already observed two 0.12 bugs disappearing on 0.13. The bugfix-backporting seems sluggish and it doesn't encourage me at all to keep using 0.12 despite it is "the most consistent experience".