feat: parallelize wizcli scans across image targets
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 68/100
Research direction
Start with posit_bakery/plugins/builtin/wizcli/suite.py and compare its run() flow with plugins/builtin/dgoss/suite.py; then read the posit_bakery/parallel/ module and the wizcli scan command entry point. Done means scans use the parallel executor with a --jobs/-j option, progress matches dgoss, and report parsing, stderr handling, and error aggregation remain unchanged.
Written by the indexing model from the issue text.
Description
Summary
WizCLISuite.run() (posit-bakery/posit_bakery/plugins/builtin/wizcli/suite.py) runs subprocess.run(...) serially in a for loop — one wizcli scan per image target. Like hadolint, this is a plain cmd: list[str] subprocess call and a good fit for the tool-agnostic posit_bakery/parallel/ module (ParallelShellExecutor/ShellTask) introduced in #588.
Scope
- Port
WizCLISuite.run()to buildShellTasks fromself.wizcli_commandsand dispatch throughParallelShellExecutor, following the pattern inplugins/builtin/dgoss/suite.py. - Add a
--jobs/-jflag to the wizcli scan command, matching thedgoss run --jobsconvention. - Preserve existing per-target report parsing (
WizScanReport.load), verbose-conditional stderr capture, and error aggregation (BakeryWizCLIError,WIZCLI_EXIT_CODE_POLICY_VIOLATIONhandling) exactly as-is; only the dispatch mechanism changes. - Update/extend the live progress table behavior to match dgoss.
Out of scope
- Changing wizcli scan policy or report contents.
Part of the investigation started in #584. See #588 for the reference implementation pattern (dgoss).
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 20
Getting set up
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.
More from posit-dev/images-shared
-
cvp:0 docker tdp:1
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
posit-dev/images-shared#757 · 2 comments ·
Maintainers usually reply within 1 day
-
bug cvp:0 docker priority/medium python tdp:1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
posit-dev/images-shared#685 ·
Maintainers usually reply within 1 day
-
slack-build-notify: no persisted alert state — causes suppressed repeat-failure and recovery alertsOpenbug cicd cvp:0 docker needs discussion observability tdp:2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
posit-dev/images-shared#677 ·
Maintainers usually reply within 1 day
-
cvp:0 docker tdp:2 tech debt
Difficulty 4/5 3-5 days Newbie friendliness 48/100
posit-dev/images-shared#795 ·
Maintainers usually reply within 1 day
-
cicd cvp:0 docker enhancement tdp:2
Difficulty 5/5 Over a week Newbie friendliness 35/100
posit-dev/images-shared#773 ·
Maintainers usually reply within 1 day
All issues in posit-dev/images-shared
Similar issues
-
customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/azure-cli#34150 · 1 comment ·
Maintainers usually reply within 1 day
-
community-request
Difficulty 1/5 Under an hour Newbie friendliness 95/100
NVIDIA-NeMo/Curator#2464 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
WeblateOrg/translation-finder#1099 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
trezor/trezor-firmware#7997 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day