From dd01aa1141b155c6564d30f6241d3dd0bcb3f8ce Mon Sep 17 00:00:00 2001 From: Nic Cope Date: Fri, 23 Aug 2024 12:31:04 -0700 Subject: [PATCH] Briefly mention how fn-pandt relates to legacy P&T Signed-off-by: Nic Cope --- content/master/guides/function-patch-and-transform.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/master/guides/function-patch-and-transform.md b/content/master/guides/function-patch-and-transform.md index 99483a4f..a356d7a0 100644 --- a/content/master/guides/function-patch-and-transform.md +++ b/content/master/guides/function-patch-and-transform.md @@ -13,6 +13,16 @@ A [patch](#create-a-patch) copies a value from one resource and _patches_ it onto another resource. A [transform](#transform-a-patch) modifies the values before applying the patch. +{{}} +All Compositions used Patch and Transform before Crossplane added +support for composition functions. + +Function Patch and Transform works like legacy `mode: Resources` Compositions, +which Crossplane deprecated in v1.17. The difference is that it uses a +`mode: Pipeline` Composition and a function instead of a `mode: Resources` +Composition. +{{< /hint >}} + Here's an example Composition that uses Function Patch and Transform. When you create an `AcmeBucket` XR that uses this Composition, Crossplane uses the template to create the Amazon S3 `Bucket` MR.