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 version has different output #12565

Closed
luckeyca opened this issue Aug 9, 2023 · 2 comments · Fixed by #12569
Closed

packer version has different output #12565

luckeyca opened this issue Aug 9, 2023 · 2 comments · Fixed by #12569
Labels
bug core Core components of Packer

Comments

@luckeyca
Copy link

luckeyca commented Aug 9, 2023

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

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

Overview of the Issue

"packer version" command output is different from "packer --version" and "packer -v" outputs.
This is different from terraform and vagrant

Reproduction Steps

  1. run "packer --version" or "packer -v", the output is "1.9.2"
  2. run "packer version", the output is "Packer v1.9.2

Packer version

From packer version

Simplified Packer Template

If the file is longer than a few dozen lines, please include the URL to the
gist of the log or use the Github detailed
format

instead of posting it directly in the issue.

Operating system and Environment details

OS, Architecture, and any other information you can provide about the
environment.

Log Fragments and crash.log files

Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.

Set the env var PACKER_LOG=1 for maximum log detail.

@luckeyca luckeyca added the bug label Aug 9, 2023
@nywilken nywilken added the core Core components of Packer label Aug 11, 2023
@nywilken
Copy link
Contributor

Thanks for reporting @luckeyca we will address this for the next release.

For context the flags -v and --version are handled by the CLI runner which just outputs the raw version string. We'll update to match the version subcommand.

nywilken added a commit that referenced this issue Aug 11, 2023
The flags -v and --version are handled by the CLI runner, which
outputs the raw version string. This change shortcuts the handling of
the flags to force Packer to run the version subcommand.

Closes: #12565
nywilken added a commit that referenced this issue Aug 28, 2023
The flags -v and --version are handled by the CLI runner, which
outputs the raw version string. This change shortcuts the handling of
the flags to force Packer to run the version subcommand.

Closes: #12565
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug core Core components of Packer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants