Nic Cope

I think it'd be a good idea to take the linter configuration from c/c and replicate it here. A while back we changed c/c to "opt-in" for all linters rather...

It seems like if I remove the `panic` from the error case everything just works fine? At least, the exact same API types are generated whether or not the error...

@MisterMX Could you provide some more background here or in #5444 about the use case for deploying development functions and using them with Crossplane? Right now that issue talks about...

> By allowing dependency resolution to be skipped on a per-dependency basis, teams can manage their configurations more effectively, especially in scenarios where certain dependencies are known to be unnecessary...

This would have helped me today. I set out to add https://github.com/golang/dep to my workspace via a `go_repository` rule. Unfortunately one of dep's `testdata/` directories contains a recursive symlink cycle...

@jayconrod No need to apologise. :) I think I'd misunderstood how straightforward what I wanted to do would be anyhow. I was under the impression I'd be able to happily...

Related: we already have https://docs.crossplane.io/v2.0/guides/implementing-safe-start/. We should cross-link it, since it'll be a good idea to implement both at once.

> As a side note, I think we should be using Watches, not Owns. Owns is for types a controller creates and manages the lifecycle of. The resolver controller doesn't...

We also discussed keeping refs, but using them as schemafied convenience aliases. So for example instead of: ```yaml spec: pipeline: - step: function-negz-compose-a-bucket functionRevisionSelector: matchLabels: crossplane.io/function-name: function-negz-compose-bucket ``` You could...

> I'm not sure what the best way to address [automatically pinning composition revisions] is under this proposal. One approach that crossed my mind was to keep using `compositionUpdatePolicy`. So...