From 6b66b601b53a3132d09b05e7c174693eb3c23d05 Mon Sep 17 00:00:00 2001 From: Guillaume Berche Date: Thu, 6 Jun 2024 15:53:48 +0200 Subject: [PATCH] Clarify claiming-existing-composite-resources: CompositeAlreadyBoundError CompositeAlreadyBoundError should be returned if a composite is already bound to a claim Fixes #783 --- content/master/concepts/claims.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/content/master/concepts/claims.md b/content/master/concepts/claims.md index 65e62f72..c6aa4a9d 100644 --- a/content/master/concepts/claims.md +++ b/content/master/concepts/claims.md @@ -138,7 +138,7 @@ If you don't use namespaces in your Kubernetes deployment Claims aren't necessar ### Claiming existing composite resources By default, creating a Claim creates a new composite resource. Claims can also -link to existing composite resources. +link to existing composite resources (if not yet referencing a claim). A use case for claiming existing composite resources may be slow to provision resources. Composite resources can be pre-provisioned and a Claim can @@ -164,6 +164,10 @@ If a Claim specifies a {{}}resourceRef{{}} that doesn't exist, Crossplane doesn't create a composite resource. +If a new Claim specifies a +{{}}resourceRef{{}} of a composite which is already referenced by another existing claim, then the new Claim will fail with a `CompositeAlreadyBoundError`. + + {{}} All Claims have a {{}}resourceRef{{}}. Manually @@ -174,6 +178,8 @@ isn't required. Crossplane fills in the with the information from the composite resource created for the Claim. {{< /hint >}} + + ## Claim connection secrets If a Claim expects connection secrets the Claim must define a @@ -204,4 +210,4 @@ spec: name: my-claim-secret ``` -For more information on connection secrets read the [Connection Secrets knowledge base article]({{}}). \ No newline at end of file +For more information on connection secrets read the [Connection Secrets knowledge base article]({{}}).