Martin Atkins

Thank you for confirming. This situation is one of the future improvements we considered when recently introducing the `removed` block type as a way to give Terraform hints and instructions...

Thanks for this feature request, @Stretch96! This is an interesting idea, but also something that doesn't really have any precedent in Terraform today. We would typically expect that, as you...

Thanks for suggesting this, @LaurentLesle! Your use of `uuid` in this example draws attention to an important design question: we'd need to decide at what point these expressions are going...

Thanks for that extra context! Since this is a situation where functions are not currently allowed, there isn't really an existing precedent to follow: we're going to be implementing something...

I find it kinda unfortunate that these URLs have ended up hard-coded in this way _at all_, but I don't really have a better idea for how to deal with...

Thanks for suggesting this, @tmccombs! I think we already have an issue somewhere that overlaps with this request, but I wasn't able to find it in quick searching. The main...

Thanks for reporting this, @oto-macenauer-absa! In case it's useful to someone who works on this issue in future, I'll note that the documentation about "overriding" parts of the backend configuration...

Hi @deitChi, Thanks for reporting this. To start, I do agree that it would be useful to include the summary counts for other kinds of action in the JSON output,...

In practice `yamldecode` supports a similar pragmatic blend of YAML v1.2 and allowances for older versions, because in practice existing YAML in the world tends not to be strictly written...

As far as I understand the YAML 1.1 spec, it's built around three fundamental structural primitives: scalars, sequences, and mappings, with two different syntaxes defined for each (flow style and...