From d3aacd477cca5c4acaa1b05b8ef7ad22d85ca05f Mon Sep 17 00:00:00 2001 From: Sambhav Kothari Date: Thu, 1 Jul 2021 08:09:59 +0100 Subject: [PATCH] Clarify output location for exported layers Signed-off-by: Sambhav Kothari --- text/0000-read-only-build-layers.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/text/0000-read-only-build-layers.md b/text/0000-read-only-build-layers.md index b828f69eb..a08a9a99d 100644 --- a/text/0000-read-only-build-layers.md +++ b/text/0000-read-only-build-layers.md @@ -59,6 +59,8 @@ Updates to the lifecycle so that `build` layers created by buildpacks should be The lifecycle will have to layerize the layers marked `build` as `true` during the `build` phase of the lifecycle instead of the `export` phase. +The layerized output from the `build` phase of lifecycle could be stored at `//@exported` (which should not clash with any buildpack IDs) where ``. The exporter will just read from this to construct the final image. + # Drawbacks [drawbacks]: #drawbacks @@ -92,7 +94,7 @@ The impact this would have on the performance of the export step. The exact deta How to handle the cases when users want a common build workspace that is cached. This will be covered in a subsequent RFC and that RFC and this RFC should be implemented as an "atomic" change to avoid existing use cases from being broken without a proper migration path. -# Spec. Changes (OPTIONAL) +# Spec. Changes [spec-changes]: #spec-changes None. \ No newline at end of file