From fe1bc63c28aac2361559b0aa23a2eeb39cc71e1a Mon Sep 17 00:00:00 2001 From: Nic Cope Date: Fri, 28 Mar 2025 22:50:34 -0700 Subject: [PATCH] Drop environment config mention in context I don't think this happens by default anymore - we use function env config Signed-off-by: Nic Cope --- content/v2.0-preview/composition/compositions.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/content/v2.0-preview/composition/compositions.md b/content/v2.0-preview/composition/compositions.md index f6559d9e..b8fbf70f 100644 --- a/content/v2.0-preview/composition/compositions.md +++ b/content/v2.0-preview/composition/compositions.md @@ -875,8 +875,3 @@ that isn't desired state. Functions can use context for this. Any function can write to the pipeline context. Crossplane passes the context to all following functions. When Crossplane has called all functions it discards the pipeline context. - -Crossplane can write context too. If you enable the alpha -[composition environment]({{}}) feature Crossplane -writes the environment to the top-level context field -`apiextensions.crossplane.io/environment`.