Nic Cope

As @Feggah alluded to, this functionality is something we explicitly avoided building in favor of 'Custom Compositions' per https://github.com/crossplane/crossplane/issues/2524. That said, I don't think we're _fundamentally opposed_ to ever adding...

@bobh66 Thanks for looking into this. I generally like the approach of enabling foreground deletion. I thought that we had ruled this approach out as something we couldn't make work,...

> @negz - what do you think about using the compositeDeletePolicy value of "Foreground" to also cause the Claim reconciler to not remove the Claim's finalizer until the Composite has...

Thanks for raising this issue @idallaserra! I'm not personally very familiar with ArgoCD. Can you help me understand exactly what the auto-pruning feature is trying to do? Is it trying...

Thanks folks. It sounds like we should address this by finding a solution to https://github.com/crossplane/crossplane/issues/2000, which should let Argo know that it should manage the claim but not the resulting...

I can't immediately find any issues, but we've had some discussion in the past about Crossplane deleting things that it didn't directly created - the quintessential example is deleting all...

@natereid72 Do you think these hooks would fit best at the MR level, or at the XR level?

I think we're also seeing an instance of https://github.com/argoproj/argo-cd/issues/5082, in which ArgoCD is unaware of the relationship between XRCs and XRs.

@jessesuen I've been meaning to find some ArgoCD maintainers to reach out to to chat about this issue; I suspect some of the work to make the two projects work...

@Shadowraze228 The connection secrets pertain to different resources. One of the reasons we store them for both the claim and the XR is that it's uncommon but possible to create...