Martin Atkins

Hi all... sorry I didn't catch the discussion here before. Changing the type of an existing attribute is pretty tricky, but I think in this case we may be able...

After some investigation and discussion in hashicorp/terraform#21709, I moved this here to represent a change to add a file size limit to this provider (smaller than the 4MB limit imposed...

Hi @phreddrick, We'll investigate the weird issue here... it looks like the `%` is escaping the `${` in a similar way that `$${` would work, as a side effect of...

Sorry, yes, the workaround I suggested was intended for provider 2.0.0. Provider 1.0.0 shouldn't need a workaround at all because it doesn't yet have the `%{...}` control sequence syntax that...

Hi @voroniys, Since you are using Terraform 0.12 you can use the `templatefile` built-in function instead of this data source. The data source continues to exist primarily to support Terraform...

Hi @oonisim, If you are using Terraform 0.12 then I strongly recommend considering `template_file` to be deprecated and using [the `templatefile` function](https://www.terraform.io/docs/configuration/functions/templatefile.html) instead. Although it's not officially deprecated in the...

Hi @so0k! Sorry for this limitation. This is indeed a general problem, caused by the fact that providers currently don't have access to a base directory to relative-ize stored paths...

Hi @Phydeauxman! Sorry this didn't work as expected. At the moment this data source is limited to dealing only with simple string values, because the provider model requires each attribute...

This provider was originally written before Terraform had a `jsondecode` function. I agree that with that function now present it would be better to have a new data source that...

Hi @bramtassyns, This is not something the Terraform team at HashiCorp is currently working on, mainly just due to focus being elsewhere. The original proposal for this provider in hashicorp/terraform#8144...