Use the Crossplane CLI instead of the Upbound CLI #13

What problem are you facing?

Modelplane currently uses the up (Upbound) CLI for project building, testing, and packaging. The project tooling is being contributed to Crossplane — up project will become crossplane project. At the same time, the CLI (crank) is being broken out of the crossplane/crossplane repo into its own repo.

For launch, Modelplane should use the Crossplane CLI rather than the Upbound CLI. Modelplane is an open-source project built on Crossplane, and its build toolchain should reflect that — contributors shouldn't need the Upbound CLI to build and test.

How could Modelplane help solve your problem?

Once the project tooling lands in the Crossplane CLI, switch upbound.yaml to whatever the Crossplane project manifest is, update the Nix flake to provide the Crossplane CLI instead of (or alongside) up, and update any documentation or CI that references up project build/up project test.