Martin Atkins

Indeed, this `~` convention is normally handled by a Unix-style shell rather than individual applications, and so usually Terraform and providers don't support it except for unusual cases where the...

Hi all! I was away from this for a long time due to working on other things, but encountered a new instance of this problem today so came back to...

After seeing the quoted snippet of the code it just suddenly felt oddly familiar and so I had a hunch that this particular thing was _very old_, and indeed in...

Thanks for sharing that, @rquadling! I now have even less context about this in my working memory than I did last time I commented :upside_down_face: but I can see in...

Hi @remilapeyre! Thanks for working on this. One small concern I have about this approach is that so far we've tried to draw a line where "plugins" don't ever directly...

Hi all! A first round of this is coming in the forthcoming Terraform v1.8. Of course, this is one of those things where having it just in Terraform Core doesn't...

Hi @makarov-roman, In that example your output value would be inferred as having a tuple type because the one of the results is from a splat expression. Therefore this error...

Hi all! Terraform v1.5 introduced a new way to import using a normal Terraform plan and apply with [extra information in the configuration](https://developer.hashicorp.com/terraform/language/import) to tell Terraform that it should plan...

Hi @willhughes-au, Support for dynamic `id` arguments in `import` blocks is coming in the forthcoming v1.6.0, which is currently in its prerelease period.

Hi @ryancurrah, Since you are using your Artifactory hostname as part of the address of your provider that means you are using Artifactory's implementation of the provider registry protocol, and...