Run strip_library_content.py inside Docker container#327
Conversation
The two Library ELM/CQL stripping steps were gated behind `DAK_ENABLED == 'true'`, which meant repos without a dak.json (e.g. smart-immunizations) never had their ELM binary data stripped from published Library XML/JSON files. Move both steps out of the DAK condition so they run for every IG build. Also run strip_library_content.py inside the Docker container for consistency with strip_library_binaries.py. https://claude.ai/code/session_01QR1WgNsJbTGkcMHbAADJv2
❌ Deployment FailedBranch: Deployment failed. Please check the build log for details. |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
🚀 Deployment StartedBranch: This comment will be updated when the deployment completes. |
Keep the DAK condition — stripping should only run for DAK-enabled repos. The remaining change from this branch is running strip_library_content.py inside the Docker container for consistency with strip_library_binaries.py (avoids file permission issues). https://claude.ai/code/session_01QR1WgNsJbTGkcMHbAADJv2
litlfred
changed the title
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
2 participants
Summary
strip_library_content.pyinside theig-runDocker container instead of on the host, matching howstrip_library_binaries.pyalready runs. This avoids file permission issues since Docker-created output files may not be writable by the host user.Test plan