-
Notifications
You must be signed in to change notification settings - Fork 104
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
a command to display available, staged, and deployed products alongside each other #466
Comments
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
anybody here? ;-) |
other than cf-gitbot of course |
Sorry, we monitor the github repo, but don't always respond quick, because our backlog surface area is beyond here at the moment. We currently have individual commands for each of the |
i basically found myself invoking all three individual commands for the sake of comparing available, staged, and deployed versions (aside: each of the commands (available-products, staged-products, and deployed-products) will not necessarily produce a list of the same ordering). so i found myself wanting to see all this information side by side. which led me to looking into building this combined command. i would be curious to know if anyone else who uses om would find this command useful. sounds like so far i'm the only one. :-) |
I think what I would prefer to see (rather than just a new command) is a combined command that has flags to show each of the three separately, and defaults to showing the combined view. Implementation shouldn't initially delete the original commands, but I would really like to see them deprecated and removed in the next major bump of
And follow the same pattern for |
i like it. |
i had coded an implementation around the time i posted this issue in a fork here: https://github.com/eitansuez/om/commits/products-command |
@eitansuez I'm thinking of digging into this in my free time to see if I can come up with a clean solution taking into account Kira's comment from above. @kcboyle Does that work for you all? |
that'd be great. my fork has a branch named "products-command" with the commits from my initial go: https://github.com/eitansuez/om/tree/products-command |
Added the first pass of this PR! |
@eitansuez I ended up writing my implementation from scratch, so let me know if you see any missing edge cases that you covered in your implementation. |
thanks. i don't think there was anything special in my implementation other than exposing the command that produced the screenshot, attempting to follow conventions and trying to reuse as much of the existing codebase. |
PR was accepted and should come out in the next release of |
awesome. thank you so much! |
as a platform engineer, i'd like a command that gives me a combined view of available, staged, and deployed products.
something along these lines:
i just forked this repo today and started working on an implementation in a branch named
products-command
.would love your feedback. let me know if that's something that'd be worth incorporating as an additional om subcommand.
The text was updated successfully, but these errors were encountered: