-
Notifications
You must be signed in to change notification settings - Fork 428
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
feat(pipeline): add pipeline ls cmd #1529
Conversation
bf738ea
to
0628075
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for doing this! Looks great. I just had a question about our ongoing migration to separate packages for our Execute() logic and whether this fits into that paradigm.
// Execute writes the pipelines. | ||
func (o *listPipelineOpts) Execute() error { | ||
var out string | ||
if o.shouldOutputJSON { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this fit into the paradigm we started with the job ls
command? Could we move this logic to the list
package? https://github.com/aws/copilot-cli/blob/mainline/internal/pkg/list/list.go It looks like this uses a lot of the same APIs and flags as the other list commands so it might go nicely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was modeling this off of the env list
command, so wasn't aware of ongoing restructuring.
30becd8
to
35823c5
Compare
Fixes #1499
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.