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

Create "troubleshoot support-bundle" subcommand to succeed the "support-bundle" command #1248

Closed
Tracked by #933
banjoh opened this issue Jun 27, 2023 · 0 comments · May be fixed by #1249
Closed
Tracked by #933

Create "troubleshoot support-bundle" subcommand to succeed the "support-bundle" command #1248

banjoh opened this issue Jun 27, 2023 · 0 comments · May be fixed by #1249

Comments

@banjoh
Copy link
Member

banjoh commented Jun 27, 2023

Describe the rationale for the suggested feature.

This issue aims to create a subcommand (troubleshoot support-bundle) which will be functionally equivalent to the current support-bundle command. This feature is part of implementing #1144 proposal which aims to improve the troubleshoot CLI

Describe the feature

  • Create a new collect subcommand that will be part of the new troubleshoot command holding all CLI functionality exposed by this project
  • Implement all necessary functionality (collect, analyse, redact & archive) using the newly proposed public API.

Additional context

The initial versions of the troubleshoot command will be release as alpha versions and will coexist with the current commands for sometime until we have the confidence that it has reached feature parity with the current ones.

@banjoh banjoh changed the title Consolidate support-bundle command into a troubleshoot subcommand Create "troubleshoot collect" subcommand to succeed the "support-bundle" command Jun 27, 2023
@banjoh banjoh changed the title Create "troubleshoot collect" subcommand to succeed the "support-bundle" command Create "troubleshoot support-bundle" subcommand to succeed the "support-bundle" command Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants