shiyuyun/wyndham-ARR
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: enable XML processing in container entry

Browse Source
This commit is contained in:
Wyndham ARR
2026-07-29 18:34:03 +08:00
parent 12881be17e
commit ad3d9878c5
13 changed files with 118 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
.project-docs/60-reflection/cases/2026-07-29-verify-all-container-entrypoints.md Normal file
View File

@@ -0,0 +1,23 @@
# 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.