From a4a1ee51f1957f8141c45cb712d1e98eca517c4f Mon Sep 17 00:00:00 2001 From: Natalie Arellano Date: Tue, 1 Aug 2023 10:01:13 -0400 Subject: [PATCH] Fix Signed-off-by: Natalie Arellano --- platform.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/platform.md b/platform.md index 1cd23fc..96bb496 100644 --- a/platform.md +++ b/platform.md @@ -1034,27 +1034,27 @@ User-provided environment variables MUST be supplied by the platform as files in Each file SHALL define a single environment variable, where the file name defines the key and the file contents define the value. -The platform SHOULD NOT set user-provided environment variables directly in the lifecycle execution environment. - User-provided environment variables that are [POSIX path variables](#posix-path-variables) MAY be modified by prior buildpacks before they are provided to a given buildpack, however the user-provided value is always prepended to the buildpack-provided value. User-provided environment variables that are not POSIX path 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. + ##### Operator-Defined Variables Operator-provided environment variables MUST be supplied by the platform as files in the `/env/` directory. Each file SHALL define a single environment variable, where the file name defines the key and the file contents define the value. -The platform SHOULD NOT set operator-provided environment variables directly in the lifecycle execution environment. - The `/env/` directory follows the [Environment Variable Modification Rules](https://github.com/buildpacks/spec/blob/main/buildpack.md#environment-variable-modification-rules) outlined in the [Buildpack Interface Specification](buildpack.md), except for the modification behavior when no period-delimited suffix is provided; when no suffix is provided, the behavior is `default`. Operator-defined environment variables MAY be modified by prior buildpacks before they are provided to a given buildpack, however the operator-defined value is always applied after the buildpack-provided value. +The platform SHOULD NOT set operator-provided environment variables directly in the lifecycle execution environment. + #### Launch Environment User-provided modifications to the process execution environment SHOULD be set directly in the lifecycle execution environment.