Nic Cope

@MisterMX @phisco do you think we should reframe this issue to reflect the decision taken in #5061? > This document proposes not promoting the Composition Environment feature to beta in...

@eloo I'm supportive of this change but there are no plans to work on it right now. If someone is interested, the first step would be putting together a one-pager...

> What I think the AWS provider should do it break it into individual providers based on the aws api group If we did take a path of allowing folks...

Reopening this since we got a new report in https://github.com/crossplane/crossplane/issues/3824. It's been a long time since I've thought about this but I _think_ the fix would be to restart the...

I'm going to close this analysis-focused issue. The problem this issue outlines is still very real and still our top priority. Going forward we've committed to (somehow) installing fewer CRDs....

* https://github.com/crossplane/crossplane/issues/4746 With Crossplane v1.14 about to ship we'll have Composition Functions in beta. Our current longer term thinking is that we'll eventually remove (or at least deprecate and freeze)...

> Building on @stevendborrelli's PR I added conditionals down to the desired resources. We wanted a single patch-and-transform function to be able to apply our global patchsets and the condition...

@haarchri Do you have a sense of how many different people/orgs have tried it? I'm trying to get a sense of whether it's been well exercised enough to merge the...

> Can we close this issue? Yes, I think so. We now have the following options available: * https://github.com/crossplane-contrib/function-go-templating - Native conditional support. * https://github.com/crossplane-contrib/function-kcl - Native conditional support. *...

I believe there is a problem (or problems) to be solved here, but I'm not convinced deterministic XR names are the right solution. Generally our philosophy is: * If you...