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

Fix: platform vars #367

Merged
merged 3 commits into from
Aug 1, 2023
Merged
Changes from 1 commit
Commits
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
Next Next commit
Fix: platform-defined env vars are not actually overridable by buildp…
…acks

Signed-off-by: Natalie Arellano <narellano@vmware.com>
natalieparellano committed Jul 24, 2023
commit 5feb0b5206de39550641333018a02e103ce67020
4 changes: 2 additions & 2 deletions platform.md
Original file line number Diff line number Diff line change
@@ -1027,7 +1027,7 @@ The platform SHOULD NOT assume any other stack-provided environment variables ar
User-provided environment variables MUST be supplied by the platform as files in the `<platform>/env/` directory.
Each file SHALL define a single environment variable, where the file name defines the key and the file contents define the value.

User-provided environment variables MAY be modified by prior buildpacks before they are provided to a given buildpack.
User-provided environment variables MAY NOT be modified by prior buildpacks before they are provided to a given buildpack.

The platform SHOULD NOT set user-provided environment variables directly in the lifecycle execution environment.

@@ -1038,7 +1038,7 @@ Operator-provided environment varaiables MUST be supplied by the platform as fil

Each file SHALL define a single environment variable, where the file name defines the key and the file contents define the value.

Operator-defined environment variables MAY be modified by subsequent buildpacks before they are provided to a given buildpack.
Operator-defined environment variables MAY NOT be modified by prior buildpacks before they are provided to a given buildpack.

The platform SHOULD NOT set operator-provided environment variables directly in the lifecycle execution environment.