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

a command to display available, staged, and deployed products alongside each other #466

Closed
eitansuez opened this issue Feb 14, 2020 · 15 comments · Fixed by #516
Closed

a command to display available, staged, and deployed products alongside each other #466

eitansuez opened this issue Feb 14, 2020 · 15 comments · Fixed by #516

Comments

@eitansuez
Copy link

eitansuez commented Feb 14, 2020

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:

om_products

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.

@cf-gitbot
Copy link
Member

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.

@eitansuez
Copy link
Author

anybody here? ;-)

@eitansuez
Copy link
Author

other than cf-gitbot of course

@jtarchie
Copy link
Contributor

jtarchie commented Feb 20, 2020

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 available, staged, and deployed states.
Why is seeing them altogether useful to the operator?
How does this help in automation?

@eitansuez
Copy link
Author

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. :-)

@kcboyle
Copy link
Contributor

kcboyle commented Feb 20, 2020

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 om. (We have an example of changes made for deprecation in the tile-metadata command -- ie, renaming the new method to include 'deprecated', editing the description, etc)

om products should return a table like the screenshot above.

om products --available should return a table almost identical to om available-products:
Note: for consistency, consider changing VERSION column to AVAILABLE

+----------------------+----------------+
|         NAME         |    AVAILABLE   |
+----------------------+----------------+
| pas-windows          | 2.8.0          |
| cf                   | 2.8.0          |
| p-healthwatch        | 1.8.0-build.66 |
| pivotal-telemetry-om | 1.0.0-build.2  |
+----------------------+----------------+

And follow the same pattern for om products --staged, and om products --deployed

@eitansuez
Copy link
Author

i like it.

@eitansuez
Copy link
Author

i had coded an implementation around the time i posted this issue in a fork here: https://github.com/eitansuez/om/commits/products-command
but it does not incorporate the ideas in kira's comments above (from feb 20).
but perhaps it can serve as a starting point.

@iplay88keys
Copy link

@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?

@eitansuez
Copy link
Author

eitansuez commented Oct 13, 2020

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
recently rebased against a slightly more up-to-date upstream.

@iplay88keys
Copy link

Added the first pass of this PR!

@iplay88keys
Copy link

@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.

@eitansuez
Copy link
Author

eitansuez commented Oct 14, 2020

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.

@kcboyle
Copy link
Contributor

kcboyle commented Oct 16, 2020

PR was accepted and should come out in the next release of om

@eitansuez
Copy link
Author

awesome. thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants