Pass explicit registry host to base-image full scans #81
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/workflows!81
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/base-image-scan-registry-host"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Authenticated base-image builds succeed at parent login, then fail before full image scanning because the reusable scan step supplies REGISTRY_HOST but omits the scanner’s required SCAN_REGISTRY_HOST. This caused base-images run 117 to stop after the Forgejo runner image built and passed smoke checks.
Map the existing
inputs.registry_hostto SCAN_REGISTRY_HOST alongside the credential pair. The existing validated input still supplies REGISTRY_HOST for the parent login. No new caller input, organization variable, credential, permission or scanner exception is introduced. Refs #80 and base-images#32.Validation: three new regressions invoke the real archived-image scanner with the actual workflow mappings and mocked external commands. They prove the corrected scan proceeds, removing the hostname reproduces run 117’s exact failure, and neither Trivy nor malware export receives credentials for another host. Base-image and Forgejo contract suites pass (26 tests total; eight Windows symlink subtests unavailable). Pinned Ruff and git diff checks pass. No container was built or run locally.
After reviewed merge, publish immutable workflow patch release
v1.30.1through this repository’s protected release workflow. Base-images PR #33 adopts matching uses/library_ref pins; hosted full scans remain pending. Leave #80 open through release/adoption verification.