liquidmetal-dev / liquidmetal-dev/flintlock
Add API endpoint to retrieve stdout/stderr
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
**Describe the solution you'd like:**
It would be good if there was an API endpoint that would be called to get the stdout/stderr of the Firecracker instance.
**Why do you want this feature:**
Its handy for debugging and operational reasons. And also in the future we could expose this via a UI.
**Anything else you would like to add:**
[Miscellaneous information that will assist in solving the issue.]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or existing API entry points. Start by locating the API implementation and how Firecracker stdout/stderr are currently captured; done means a documented endpoint can retrieve both streams for a Firecracker instance and has coverage for the response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100