I would like to deal with this issue if it is in fact a bug.

Thanks @gstvcruz for the report

I just tried on my local machine seems like you're right. it does look like a bug. If you want to take a bite at it, be my guest! We warmly welcome contribution :)

When parsing a packer template, there are four stages: decoding the required plugins block, decoding input variables, decoding data sources, and parsing local variable blocks.

Each stage processes the file's body content to validate the arguments and block types for every block in the file. As a result, the same error message may be appended to the output at each stage for unsupported block types.

I'm new to Go and have never contributed to an open-source project before, especially one of this size. However, I think I'm onto something. I suppose it’s just a matter of avoiding unnecessary appendages—perhaps by checking the already appended message summary against the summary of the message to be appended? Another simpler approach would be to just remove duplicates from the output, which comes from a slice of error messages.

It seems I've fixed it! Every stage was checking for invalid arguments or unsupported block types using the same function, so I refactored it into a for loop to check every file instead. All tests have passed. I'll review the CONTRIBUTING.md file to figure out the next steps for integrating these changes.