spec
spec copied to clipboard
Specification for Cloud Native Buildpacks
[RFC 0076] Require `CNB_{USER,GROUP}_SID` instead of `CNB_{USER,GROUP}_ID` on windows stack images
[RFC 0076](https://github.com/buildpacks/rfcs/blob/main/text/0076-windows-security-identifiers.md) https://github.com/buildpacks/rfcs/pull/133 * Replace CNB_USER_ID and CNB_GROUP_ID with CNB_USER_SID and CNB_GROUP_SID on windows stack images * Replace `-uid` and `-gid` flags with `-usid` and `-gsid` flags for builds in...
## Context I was building a simple Ruby CNB when I came across this behavior. I prepended `/layers/heroku_ruby/ruby/bin` to the PATH, but found that `echo $PATH` ended up being the...
Currently there is no clear indication as to what fields are need for a bare minimum valid `buildpack.toml` file. I feel like this would be valuable information to have as...
I suggest that we remove this requirement entirely given that we haven't thought about how to handle the case where we change or remove this file between platform APIs. The...
The registry authentication chapter (ihttps://github.com/buildpacks/spec/blob/main/platform.md#registry-authentication) mentions `CNB_REGISTRY_AUTH` as a way to provide authentication to a registry. Unfortunately I didn't find how exactly this JSON is structured. Is there a schema?...
[RFC 0073](https://github.com/buildpacks/rfcs/blob/main/text/0073-offline-buildpackages.md) buildpacks/rfcs#81 * Update `buildpack.toml` to include assets field * Specify that the lifecycle will provide buildpacks the location of the asset directory at build time
This issue have been automatically created from pull request buildpacks/rfcs#172.
From https://github.com/buildpacks/spec/pull/193#discussion_r577760705 The builder spec should define how builders could support multiple platform API versions, assuming the lifecycle they contain supports said versions. For example, suppose we re-name a key...
This issue have been automatically created from pull request buildpacks/rfcs#172.