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.

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

Add sbom as a reserved buildpack ID #281

Merged
merged 1 commit into from
Jan 12, 2022
Merged

Add sbom as a reserved buildpack ID #281

merged 1 commit into from
Jan 12, 2022

Conversation

natalieparellano
Copy link
Member

This technically should have gone into buildpack/0.8. Because we are putting sbom files in /layers/sbom, sbom is now a reserved buildpack ID.

Signed-off-by: Natalie Arellano <narellano@vmware.com>
@natalieparellano natalieparellano requested a review from a team as a code owner December 15, 2021 17:23
@hone hone added this to the Buildpack 0.8 milestone Dec 15, 2021
Copy link
Member

@ekcasey ekcasey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense.

If we required the buildpack ID to be in the format <namespace>/<name> (like the registry does) we wouldn't need this list. But I don't remember why we didn't spec that requirement previously, and I wouldn't want that conversation to prevent us from adding this quick fix.

@@ -1060,7 +1060,7 @@ Buildpack authors MUST choose a globally unique ID, for example: "io.buildpacks.

*Key: `id = "<buildpack ID>"`*
- MUST only contain numbers, letters, and the characters `.`, `/`, and `-`.
- MUST NOT be `config` or `app`.
- MUST NOT be `config`, `app`, or `sbom`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we actually need to reserve app anymore?

@hone hone merged commit d0ea5ba into buildpack/0.8 Jan 12, 2022
@hone hone deleted the reserved-ids branch January 12, 2022 19:16
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.

5 participants