refactor: make get deployment more useful by using build name #294
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.
Checklist
To get the status of a build currently using the CLI, you need to
list deployments
of an environment, and then search for the build you know by its name.This makes it possible now to use
get deployment --project $project --environment $environment --name lagoon-build-abcdef
and get the build status directly, with an optional--logs
flag to return the logs of that buildThis is a breaking change of the older
get deployment
which required theremote id
of a build, and only returned the logs. But this is more useful than the previous command was.Changelog Entry