This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
CLI display improvements to operations #3081
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when you run an operation on the CLI, there's no great way to know later which operation you just ran. I.e. you can run
waypoint build, and later runwaypoint artifact list-buildsand assume the highest-numbered build is the one you just created, but you can't really know for sure. This also makes it hard to correlate between the CLI and the UI.This change adds a new step group, printing
⠏ Running build v18, or⠏ Running deploy v3, or equivalent, to every operation. It completes when the full op completes.For artifacts in particular, this also prints the id of the produced artifact, if any (which is distinct from the build)
Example: