-
Notifications
You must be signed in to change notification settings - Fork 43
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
Provide context when viewing broker inventory of what each machine is #306
Comments
|
JacobCallahan
added a commit
to JacobCallahan/broker
that referenced
this issue
Sep 6, 2024
This provides a styled middle ground between the default minimal view and the much more verbose detailed view. This also give us an opportunity to explore different output styling with rich. fixes SatelliteQE#306
JacobCallahan
added a commit
that referenced
this issue
Sep 9, 2024
This provides a styled middle ground between the default minimal view and the much more verbose detailed view. This also give us an opportunity to explore different output styling with rich. fixes #306
JacobCallahan
added a commit
to JacobCallahan/broker
that referenced
this issue
Jan 21, 2025
This provides a styled middle ground between the default minimal view and the much more verbose detailed view. This also give us an opportunity to explore different output styling with rich. fixes SatelliteQE#306
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would love to have a way when viewing
broker inventory
to be able to define and see context of the machines in order to remember what each was. For example, I often use the--nick
feature to spin up machines based on a "profile". That nick is typically descriptive, e.g.satellite-6.15
. When I am staring at a list of multiple machines in inventory I have to guess which was which, accessing each and reminding myself which is which to find the one I need. This would be great to extend to the operating system running as well.Note: I am not saying that it's the nick that has to be used, could be some description property or something else entirely that provides that context.
The text was updated successfully, but these errors were encountered: