slimtoolkit / slimtoolkit/slim
Refactor `--http-probe-exec` and `--http-probe-exec-file` to be separate from HTTP probes and add its own `continue-after` mode
Open
Nobody has claimed this yet.
feature
help wanted
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
These flags represent app probes that you configure to run when docker-slim is doing dynamic analysis. It should be done separately from the existing HTTP probes.
New names:
--app-exec (was --http-probe-exec)
--app-exec-file (was --http-probe-exec-file)
New continue-after mode: app
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
Trace the CLI definitions and dynamic-analysis handling for --http-probe-exec, --http-probe-exec-file, and continue-after. Separate the app probe flags from HTTP probes, add --app-exec and --app-exec-file, and make continue-after=app work; verify the existing HTTP behavior remains distinct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100