CLI docs

[plumbis]

Includes CLI docs covering everything except beta trace and beta xpkg init.

Signed-off-by: Pete Lumbis pete@upbound.io

[netlify]

✅ Deploy Preview for crossplane ready!

Name	Link
🔨 Latest commit	e1cb0f9
🔍 Latest deploy log	https://app.netlify.com/sites/crossplane/deploys/6540315dd5900900081793e5
😎 Deploy Preview	https://deploy-preview-584--crossplane.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: Accessibility: Best Practices: SEO: PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jbw976]

This is a fantastic effort @plumbis to get our CLI docs going - I really like it and appreciate it!! dropped a few comments that may help with clarifying some of the content here, feel free to push back on anything you think doesn't actually improve things 😇

[jbw976]

interesting, i didn't know we had this functionality 😂 - does it look for existing installed packages from the same registry, org, and repo then tries to upgrade what it finds to the new version here? 🤔

[negz]

No, it just defaults the name from the package the same way xpkg install does if you omit the name.

[phisco]

I really appreciate your effort here @plumbis, but are we really sure we are going to be able to maintain this? Looking at other examples such as istioctl and kubectl which then points to https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands. It feels like the common pattern is to provide an high level overview of common flags and functionalities, showcase common scenarios and then point to the generated documentation directly for all the nitty gritty details, which would make sense to me as a user.

[plumbis]

I think the concern is valid but if we have enough commands that it's a problem, that's a good problem to have.

For now I'd like to keep it manually updated.