Nic Cope

In Crossplane you could imagine dry-run happening at two layers: 1. Given a claim/XR, what set of composed resources would Crossplane desire? 2. Given a set of desired composed resources,...

> Wonder if the updated charter of Crossplane that includes developer experience and a CLI tool could include this. Will we start publishing an official Crossplane CLI? It does, and...

I wrote up some ideas on an architecture that could enable end-to-end, cloud-to-claim `xrender`-like dry-run functionality in https://github.com/crossplane/crossplane/issues/4723. I think this would let us build a good user experience, but...

> is specifying a manifest with functions required on the xrender command line? Yes, `xrender` only works with Functions and requires to give it a manifest of Functions so that...

@wojciechka I don't think `crossplane beta render` will support "native" resources based Composition. This is because: * It's awkward to do. The `crossplane` CLI would need to compile in the...

> Is it still scheduled to be out later this month? It is! Or I think technically we're scheduled for November 1st.

> I think it make sense to compose existed composite resource claims into a new composite resource. The claim itself is a namespaced resource. You can already compose XRs into...

At this point I don't think Crossplane is going to support composing arbitrary Kubernetes resources (except via providers such as provider-kubernetes and provider-helm), at least not without "Crossplane v2" level...

This is a duplicate of https://github.com/crossplane/crossplane/issues/2608 - let's discuss this there.

@jeanduplessis I logged in using GitHub. If you do, are you able to manage the Crossplane project?