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

Sort output of plan status and history commands #1371

Merged
merged 2 commits into from
Mar 3, 2020

Conversation

yankcrime
Copy link
Member

@yankcrime yankcrime commented Feb 29, 2020

What this PR does / why we need it:
Alphabetise (by plan) the output of the plan status and history commands so that they're consistent with each run. This helps human operators when monitoring a deployment.

Fixes #1354

Copy link
Member

@ANeumann82 ANeumann82 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, I'm looking forward to have this in :)

pkg/kudoctl/cmd/plan/plan_status.go Outdated Show resolved Hide resolved
pkg/kudoctl/cmd/plan/plan_status.go Outdated Show resolved Hide resolved
@yankcrime yankcrime force-pushed the plan_status_order branch 2 times, most recently from cdd8ee2 to ae9d3fd Compare March 1, 2020 15:55
@yankcrime yankcrime changed the title Sort output of plan status command Sort output of plan status and history commands Mar 2, 2020
Copy link
Member

@ANeumann82 ANeumann82 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still good, I wouldn't mind having a temporary variable in the plan_history.go though.

Copy link
Contributor

@zen-dog zen-dog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm!

Copy link
Member

@nfnt nfnt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

pkg/kudoctl/cmd/plan/plan_status.go Outdated Show resolved Hide resolved
Copy link
Member

@kensipe kensipe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs a test in plan_status_test.go

part of requesting a test is to ensure that it is testable... with a timestamp formatted output it isn't clear.

pkg/kudoctl/cmd/plan/plan_status.go Outdated Show resolved Hide resolved
Alphabetise (by plan) the output of the plan status and history commands
so that they're consistent with each run.  This helps human operators
when monitoring a deployment.

Signed-off-by: Nick Jones <nick@dischord.org>
Include timestamps in output, and define more than one plan.

Signed-off-by: Nick Jones <nick@dischord.org>
Copy link
Member

@kensipe kensipe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@kensipe kensipe merged commit 4f1fce8 into kudobuilder:master Mar 3, 2020
@yankcrime yankcrime deleted the plan_status_order branch March 3, 2020 17:45
runyontr pushed a commit that referenced this pull request Mar 11, 2020
* Sort output of plan status and plan history commands

Alphabetise (by plan) the output of the plan status and history commands
so that they're consistent with each run.  This helps human operators
when monitoring a deployment.

Signed-off-by: Nick Jones <nick@dischord.org>
Signed-off-by: Thomas Runyon <runyontr@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/cli kubectl kudo a.k.a. kudoctl
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Plan status output should be sorted
5 participants