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

Backport of cli: improve output of eval commands into release/1.3.x #13638

Merged

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #13581 to be assessed for backporting due to the inclusion of the label backport/1.3.x.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.


Use the same output format when listing multiple evals in the eval list command and when eval status <prefix> matches more than one
eval.

Include the eval namespace in all output formats and always include the
job ID in eval status since, even node-update evals are related to a
job.

Add Node ID to the evals table output to help differentiate
node-update evals.

@hashicorp-cla
Copy link

hashicorp-cla commented Jul 7, 2022

CLA assistant check
All committers have signed the CLA.

Use the same output format when listing multiple evals in the `eval
list` command and when `eval status <prefix>` matches more than one
eval.

Include the eval namespace in all output formats and always include the
job ID in `eval status` since, even `node-update` evals are related to a
job.

Add Node ID to the evals table output to help differentiate
`node-update` evals.

Co-authored-by: James Rasell <jrasell@hashicorp.com>
@lgfa29 lgfa29 force-pushed the backport/f-improve-eval-cli-output/gladly-ready-pup branch from cdf1141 to 2d78ace Compare July 7, 2022 19:22
@lgfa29 lgfa29 merged commit 3861720 into release/1.3.x Jul 8, 2022
@lgfa29 lgfa29 deleted the backport/f-improve-eval-cli-output/gladly-ready-pup branch July 8, 2022 14:37
@github-actions
Copy link

github-actions bot commented Nov 6, 2022

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, 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 Nov 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants