Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove target.id from the lifecycle #375

Merged
merged 1 commit into from
Aug 3, 2023
Merged

Remove target.id from the lifecycle #375

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions platform.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1240,7 +1240,6 @@ The image reference will be mapped to a path in the layout directory following t
reference = "<image reference>"
extend = false
[target]
id = "<target identifer>"
os = "<OS name>"
arch = "<architecture>"
variant = "<architecture variant>"
Expand All @@ -1263,7 +1262,6 @@ Where:
- The ID of an image in a docker daemon
- The path to an image in OCI layout format
- `run-image.image` MUST be the platform- or extension-provided image name
- `run-image.target.id` is optional and MUST be the value of the label `io.buildpacks.base.id`
- `run-image.target` contains the [target data](#target-data) for the image
- If target distribution data is missing, it will be inferred from `/etc/os-release` for Linux images; furthermore, if the image contains the label `io.buildpacks.stack.id` with value `io.buildpacks.stacks.bionic`, the lifecycle SHALL assume the following values:
- `run-image.target.os = "linux"`
Expand Down