24 lines
1.0 KiB
Markdown
24 lines
1.0 KiB
Markdown
# Verify every production container entrypoint
|
|
|
|
## Trigger
|
|
|
|
The deployment snapshot explicitly enabled XML processing in the Compose Web command,
|
|
but the Dockerfile default CMD omitted `--enable-processing`. A platform that built and
|
|
ran the image directly therefore served the page with processing disabled even when all
|
|
runtime environment values were present.
|
|
|
|
## Lesson
|
|
|
|
A deployment feature flag is not verified merely because one orchestrator profile
|
|
contains it. Every supported executable entrypoint must agree: image CMD, Compose
|
|
command and any documented platform override. Runtime readiness remains a separate
|
|
gate and must not be replaced by a static flag assertion.
|
|
|
|
## Action
|
|
|
|
- Parse the Dockerfile CMD in an automated test and require the intended processing flag.
|
|
- Assert that unrelated mutation flags remain absent.
|
|
- Keep the source CLI default closed and require `/api/health` to report
|
|
`processing_ready=true` after deployment.
|
|
- Tell operators that replacing CMD/command also replaces the feature flag.
|