Reject missing required values before service startup
The service starts with an empty callback base URL and fails only when the first delivery completes.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Schema validation · Fail-closed startup
Estimated field mix
- DevOps70%
- Quality engineering30%
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 notification service uses environment files assembled by shell scripts. Defaults differ by machine, secret values appear in diagnostics, and emergency flags have no expiry. Build a typed local configuration compiler with fake secret references and synthetic environments; no real credentials or notification providers are supplied.
Setup prerequisites
- Configuration precedence
- Schema validation
- Least privilege
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Schema distinguishes required, optional, and defaulted values
- Validation reports all safe field errors together
- Invalid configuration prevents provider initialization
Implementation constraints
- Defaults must be explicit in the versioned schema and safe for every environment that uses them.
Verification to include
- Validate complete development and production-like fixture configurations.
- Remove several required fields and confirm providers are never constructed.
Deliverables
- Typed configuration schema and startup tests
Rollout and recovery
Run validation as a pre-deployment gate before enforcing it at startup.
Value of the work
For the engineer: Practice configuration as a reviewed contract with safe diagnostics, provenance, and rollback.
For the team: Review environment changes before deployment and reduce outages caused by missing, stale, or silently defaulted settings.
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.