mirror of https://github.com/crossplane/docs.git
docs: clarify content of desired resources in composition functions (#506)
This commit is contained in:
parent
5372be9a3a
commit
872d68e35c
|
@ -348,11 +348,18 @@ The `desired` state of the XR and composed resources is how your Function tells
|
|||
Crossplane what it should do. Crossplane 'bootstraps' the initial desired state
|
||||
passed to a Function pipeline with:
|
||||
|
||||
* A copy of the observed state of the XR.
|
||||
* A copy of the observed state of any existing composed resources.
|
||||
* A copy of the observed state of the composite resource (XR).
|
||||
* A copy of the observed state of any existing composed resources produced
|
||||
from the `resources` array.
|
||||
* Any new composed resources or modifications to observed resources produced
|
||||
from the `resources` array.
|
||||
|
||||
{{< hint "note" >}}
|
||||
The initial desired state doesn't include any copies of observed resources
|
||||
produced by the function pipeline. When using multiple functions each function
|
||||
passes their desired resources output as input to the next pipeline function.
|
||||
{{< /hint >}}
|
||||
|
||||
When adding a new desired resource to the `desired.resources` array you don't
|
||||
need to:
|
||||
|
||||
|
|
Loading…
Reference in New Issue