Exclude local credentials and bulky artifacts from the image context
A developer notices an environment file and test recordings copied into the service image.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Container builds · Secrets handling
Estimated field mix
- Security50%
- Platform engineering30%
- Developer tooling20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional reporting API is rebuilt separately for staging and production. Different dependency resolutions and mutable tags make incident rollback unreliable.
Setup prerequisites
- Create a tiny local HTTP service and nonprivileged image build.
- Use synthetic registries or provider fixtures; no production deployment.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Allow only required source and build inputs into context.
- Exclude environment files, VCS metadata and generated recordings.
- Add a safe inspection command that lists included paths.
Implementation constraints
- Create fake secrets for tests; never scan or print real secret values.
Verification to include
- Build a minimal synthetic service context.
- Add a fake credential file and verify it is absent from context and image.
Deliverables
- Context allowlist and image-content check
Rollout and recovery
Apply before the next image build; discard affected disposable images.
Value of the work
For the engineer: Practice artifact identity, least privilege and reproducible delivery.
For the team: Review whether deployed bytes can be traced and rolled back reliably.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.