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

troubleshoot should be able to show interactive results on a bundle that's already been collected #794

Closed
adamancini opened this issue Oct 19, 2022 · 2 comments
Labels
type::feature New feature or request

Comments

@adamancini
Copy link
Member

Describe the rationale for the suggested feature.

After the analysis stage, an interactive terminal UI is presented to display the results of the analysis. It might be nice to be able to show this screen post-collection if you already have a support bundle.

It kind of seems like kubectl support-bundle analyze is set up to do that, but it requires that you pass in an analyzer spec and a support bundle file - not quite clear on the intent for how this would be used, except maybe to run new/additional analyzers that were not in the original spec?

But in any case, if the analyzer results file is in the .tar.gz archive, we should be able to simply present the results to the user.

Describe the feature

Perhaps something like kubectl support-bundle view-results that will look for analysis.json in a support bundle archive and jump straight to the interactive results TUI.

@adamancini adamancini added the type::feature New feature or request label Oct 19, 2022
@adamancini adamancini changed the title troubleshoot should be able to show the analysis interactive screen for viewing results post-collection troubleshoot should be able to show interactive results on a bundle that's already been collected Oct 19, 2022
@xavpaice xavpaice moved this to Near Term in Troubleshoot Roadmap Dec 21, 2022
@xavpaice
Copy link
Member

This should be rolled into the new CLI, design in #934

@xavpaice xavpaice moved this from Near Term to Long term & Epics in Troubleshoot Roadmap May 17, 2023
@github-project-automation github-project-automation bot moved this from Long term & Epics to Done in Troubleshoot Roadmap May 28, 2023
@xavpaice
Copy link
Member

closing as #933 will handle this requirement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants