Piping expression for variable to packer console in powershell shows no output
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 15.8k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
> packer version
Packer v1.9.2
> get-content .\file.pkr.hcl
variable "flavor" {
type = string
default = "strawberry"
}
$ echo "var.flavor" | packer console .\file.pkr.hcl
>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported PowerShell pipeline with packer console .\file.pkr.hcl and the variable definition shown in the issue. Trace the packer console command's handling of piped input and verify that the expression produces the expected variable value rather than blank output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100