dynamic-blocks: An argument named "key" is not expected here

[nextus]

Overview of the Issue

According to the documentation, I have to use key and value in the content block but it doesn't work:

  on ./packer.pkr.hcl line 56, in source "amazon-ebs" "ebs":
  56:       key   = tag.key

An argument named "key" is not expected here.

It seems this default schema is applied:

packer/hcl2template/types.variables.go

Line 295 in 79f1fab

Blocks: []hcl.BlockHeaderSchema{

I replaced in my configuration key to name as a workaround and everything starts working but this is implicit behavior.

Reproduction Steps

Run build with dynamic block from the documentation.

Packer version

1.5.5

[sylviamoss]

Hey there, thanks for reaching out! We'll try to take a look for the next release.
Could you please provide us your simplified Packer hcl template?

[azr]

Hello there ! I first implemented it using the key key but then later changed it to name to remain consistent with filter/subnet_filters/etc., updating the docs now.

[azr]

Ah scratch that, it's a little more complex. So when I implemented #8889 to allow to use tags/filters/subnetfilters key value maps I used the key "name" everywhere for consistency across Packer builders and Terraform I though; also it made implementation simpler.

But what Terraform providers do is using the naming convention of the upstream service. For example for the tags aws uses key/value (docs) and for VPC filters it is name/value (docs).

We'll soon work on fixing this to have this behaviour, note that this will be a breaking change.

[azr]

Hello there, #9078 should address this. Binaries can be found here: artifacts.

[ghost]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.