hyperweb-io / hyperweb-io/starship
feature: ability to dump starship state/logs
- Dominant language
- TypeScript
- Stars
- 77
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
## Overview
When there is an error or there needs to be debugging required, then we need a way to dump the whole state of the network.
## Proposal
Based on the config file, create a dump dir that fetches the:
* logs of each component
* k8s definations that spun them up
* config files
* scripts etc
> We could make this part of starship cli, `starship export` command that can perform the export.
## Additional requirements
Should be callable from test cases itself. Incase of failure in a test case, an export should be performed so as to be able to debug.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the starship CLI entry point and the test-case integration points. Define how an export command would collect component logs, Kubernetes definitions, configuration files, and scripts from the configured network. Done means the export can be invoked from the CLI and automatically from failing tests, producing a complete debug directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- cli, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100