-
Notifications
You must be signed in to change notification settings - Fork 184
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
glasskube describe
command
#241
Comments
Hey @christophenne Would like to give it a try! |
Hi @bishal7679, |
Np @christophenne |
@bishal7679 since the #172 is about the be closed soon, you could work on the describe command. Are you still interested? |
Yes! would like to give it a try |
@bishal7679 thanks! I provided some additional information in the description above, if you need anything else, don't hesitate to ask here or on discord. |
Yeah! I'm getting my hands dirty with it and will let you know further update |
Hi @bishal7679, I hope you are doing well. I just wanted to check in and ask how you are doing with this issue. Is there anything we can help you with? If so, please don't hesitate to reach out. |
@christophenne I really apologize! |
@bishal7679 no worries! Thanks for letting us know, please have a quick look in Discord so we can synchronize on how we proceed. |
Is your feature request related to a problem? Please describe.
We are working on the package detail page on the UI (#172 ), so there should be an equivalent command for the CLI to show all relevant package details. Just like on the UI, this should work for both uninstalled and installed packages, and the status of the package should be shown.
Describe the solution you'd like
glasskube describe [package-name]
should print the same package details to the console as we show in the UI.Additional context
Depends on #172 to develop the client functionality that can be used by both layers.
For implementing this task, reuse
DescribePackage
frompkg/describe/describe.go
, which contains all the logic to fetch all the relevant data which should be displayed.The text was updated successfully, but these errors were encountered: