Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

packer fmt: support formatting multiple named templates #12883

Open
tomeon opened this issue Mar 12, 2024 · 1 comment
Open

packer fmt: support formatting multiple named templates #12883

tomeon opened this issue Mar 12, 2024 · 1 comment
Labels
enhancement stage/accepted Confirmed, and intend to work on. No timeline commitment though.

Comments

@tomeon
Copy link

tomeon commented Mar 12, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

This is a request for supporting multiple template and/or directory arguments to packer fmt, rather than the current limitation to a single template (or directory, or stdin). Basically hashicorp/terraform#28191, but for Packer. Related: numtide/treefmt-nix#169.

Use Case(s)

  1. Support for/compliance with the treefmt formatter specification, and
  2. Greater user control over the precise set of files-to-be-formatted.

Potential configuration

$ packer fmt this.pkr.hcl yet/another.pkrvars.hcl but/wait/theres/more.pkr.hcl

Potential References

Thank you in advance for your consideration!

@nywilken
Copy link
Contributor

@tomeon thanks for opening up this request. This looks like a nice enhancement for the fmt command. Thanks for bubbling this up.

@nywilken nywilken added the stage/accepted Confirmed, and intend to work on. No timeline commitment though. label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement stage/accepted Confirmed, and intend to work on. No timeline commitment though.
Projects
None yet
Development

No branches or pull requests

2 participants