Skip to content

Commit

Permalink
Update text/0000-layer-metadata-files.md
Browse files Browse the repository at this point in the history
Signed-off-by: Sambhav Kothari <skothari44@bloomberg.net>

Co-authored-by: Natalie Arellano <narellano@vmware.com>
  • Loading branch information
sambhav and natalieparellano authored Apr 7, 2021
1 parent 344cd07 commit 3b01757
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions text/0000-layer-metadata-files.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ The top level `<buildpack-workspace>` would house any files and folder that are
# How it Works
[how-it-works]: #how-it-works

The lifecycle would stages the reference `<layers>` directory would now take in `<buildpack-workspace>` directory instead. The behavior with respect to the various metadata files and the lifecycle would remain the same, however the `analysis`, `restore`, `build` and `export` phases would have to be updated to look for the various layer directories inside the `layers` sub-folder in the `buildpack-workspace`.
The lifecycle phases that reference the `<layers>` directory would now take in `<buildpack-workspace>` directory instead. The behavior with respect to the various metadata files and the lifecycle would remain the same, however the `analysis`, `restore`, `build` and `export` phases would have to be updated to look for the various layer directories inside the `layers` sub-folder in the `buildpack-workspace`.

# Drawbacks
[drawbacks]: #drawbacks
Expand Down Expand Up @@ -96,4 +96,3 @@ We keep having this ambiguity and possible issues in the future when we want to
[unresolved-questions]: #unresolved-questions

<!-- TODO -->

0 comments on commit 3b01757

Please sign in to comment.