Skip to content

fix: stage recipe inputs relative to the service build context - #23

Merged
antoinetoussaint-byte merged 1 commit into
mainfrom
fix/recipe-output-layout
Sep 22, 2026
Merged

antoinetoussaint-byte merged 1 commit into
mainfrom
fix/recipe-output-layout

Conversation

@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor

Fix at the owning agent: DockerBuildRecipe.context is service-relative, while dockerfile is output_directory-relative. The agent emitted builder/envoy.yaml only beneath output_directory, but the real CLI supplies service/builder and invokes Docker from the service. This produced builder/builder/envoy.yaml, while COPY required builder/envoy.yaml. Stage the bootstrap in the service context and emit the Dockerfile directly into the requested recipe directory. Regression now checks COPY sources against the service root, and Docker buildx --check uses the protocol-defined context. Full suite passed (47.162s), build/vet passed. Actual release-grade conformance will rerun after merging. Part of codefly-dev/core#622.

@antoinetoussaint-byte
antoinetoussaint-byte merged commit f5e461f into main Sep 22, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant