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

#266 建立於 2021年12月27日

在 GitHub 查看
 (4 留言) (1 反應) (0 負責人)Go (17,694 star) (673 fork)batch import
featurehelp wanted

描述

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

貢獻者指南

技術棧
go
領域
backend
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GoCLI flagsDocker
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Identify all locations in the codebase that reference http probe exec and http probe exec file flags. Create new flags app exec and app exec file with identical behavior but separate from HTTP probe handling. Implement a new continue after mode 'app' that waits for execution of these app exec probes. Remove or deprecate the old flags and update the CLI help text, documentation, and any tests that cover these flags. The relevant files are likely in the cmd/ and pkg/ directories of the repository.