Skip to content
Buildpack API v3, a specification for Cloud Native Buildpacks
Branch: master
Clone or download
sclevine Merge pull request #55 from buildpack/clear-env
Load user-provided variables by default
Latest commit f8803b6 Aug 13, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
extensions Withdraw deltas extension Feb 20, 2019
img Fix launch image width Oct 8, 2018
.gitignore Update diagrams to reflect spec Oct 2, 2018
CODEOWNERS Proper team name format Jul 17, 2019
LICENSE Initial commit Aug 26, 2018
OWNERS
README.md Add distribution spec reference to README Aug 4, 2019
buildpack.md Update buildpack spec to cover clear-env Aug 9, 2019
distribution.md Add clear-env to buildpack.toml Aug 9, 2019
platform.md Add support for stage-specific mixins Aug 6, 2019

README.md

Buildpack API v3 - Specification

This specification defines interactions between a platform, a lifecycle, a number of buildpacks, and an application

  1. For the purpose of transforming that application into an OCI image and
  2. For the purpose of developing or executing automated tests on that application.

A buildpack is software that partially or completely transforms application source code into runnable artifacts.

A lifecycle is software that orchestrates buildpacks and transforms the resulting artifacts into an OCI image.

A platform is software that orchestrates a lifecycle to make buildpack functionality available to end-users such as application developers.

Notational Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119.

The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the rationale for the C99 standard.

An implementation is not compliant if it fails to satisfy one or more of the MUST, MUST NOT, REQUIRED, SHALL, or SHALL NOT requirements for the protocols it implements. An implementation is compliant if it satisfies all the MUST, MUST NOT, REQUIRED, SHALL, and SHALL NOT requirements for the protocols it implements.

Sections

You can’t perform that action at this time.