Focused crawls are collections of frequently-updated webcrawl data from narrow (as opposed to broad or wide) web crawls, often focused on a single domain or subdomain.
A composite resource claim (XRC) is a namespaced proxy for a composite resource (XR). Both types have an almost identical schema. When an XRC is created an XR is typically created in response, and the claim's spec.compositionRef and spec.compositionSelector are propagated to the XR. Currently if you create a claim with only a composition selector, or with neither a reference or a selector (relying on the XRD's default or enforced composition) the claim's composition reference is never updated to reflect the composition selected by the XR.
We mostly "late initialize" a claim from its XR, but when doing so we ignore any fields shared with the XR. This includes the composition reference, selector, etc per
Create a claim with a composition selector and no composition reference (e.g. the GCP claim from the Crossplane 1.1 getting started guide) and observe that the XR has its composition reference set, but the claim never does.
What environment did it happen in?
Crossplane version: 1.1
The text was updated successfully, but these errors were encountered:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
What happened?
A composite resource claim (XRC) is a namespaced proxy for a composite resource (XR). Both types have an almost identical schema. When an XRC is created an XR is typically created in response, and the claim's
spec.compositionRefandspec.compositionSelectorare propagated to the XR. Currently if you create a claim with only a composition selector, or with neither a reference or a selector (relying on the XRD's default or enforced composition) the claim's composition reference is never updated to reflect the composition selected by the XR.We mostly "late initialize" a claim from its XR, but when doing so we ignore any fields shared with the XR. This includes the composition reference, selector, etc per
crossplane/internal/controller/apiextensions/claim/configurator.go
Line 149 in 39217a2
How can we reproduce it?
Create a claim with a composition selector and no composition reference (e.g. the GCP claim from the Crossplane 1.1 getting started guide) and observe that the XR has its composition reference set, but the claim never does.
What environment did it happen in?
Crossplane version: 1.1
The text was updated successfully, but these errors were encountered: