From 01c36d1159f33ea414817d64881f59417222999f Mon Sep 17 00:00:00 2001 From: Nic Cope Date: Wed, 13 Aug 2025 12:40:03 -0700 Subject: [PATCH] Composition functions don't run on delete Signed-off-by: Nic Cope --- content/master/composition/compositions.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/content/master/composition/compositions.md b/content/master/composition/compositions.md index d0e00217..81e71152 100644 --- a/content/master/composition/compositions.md +++ b/content/master/composition/compositions.md @@ -140,7 +140,12 @@ reports `True`. Crossplane calls a Function to determine what resources it should create when you create a composite resource. The Function also tells Crossplane what to do -with these resources when you update or delete a composite resource. +with these resources when you update a composite resource. + +{{}} +Composition functions don't run when you delete a composite resource. +Crossplane handles deletion of composed resources automatically. +{{< /hint >}} When Crossplane calls a Function it sends it the current state of the composite resource. It also sends it the current state of any resources the composite @@ -576,7 +581,7 @@ sequenceDiagram Crossplane Pod->>+API Server: Apply desired composed resources ``` -When you create, update, or delete a composite resource that uses composition +When you create or update a composite resource that uses composition functions Crossplane calls each function in the order they appear in the Composition's pipeline. Crossplane calls each function by sending it a gRPC RunFunctionRequest. The function must respond with a gRPC RunFunctionResponse.