These all had quite a lot of interactions so I had to do them together.
Note we can't bump to Kubernetes v0.31.0 because it's newer than what
the latest crossplane-runtime release is using. We'll need to update
crossplane-runtime first.
I'm also seriously questioning keeping the dependency on provider-aws.
It's massive and has a lot of painful dependencies to fix when we update
the import. On the other hand, I experimented with e.g. using
provider-nop or provider-kubernetes for examples and didn't like it.
Signed-off-by: Nic Cope <nicc@rk0n.org>
v1 is currently identical to v1beta1. Upstream we have automation that
makes sure the two protos are identical (apart from their package).
Signed-off-by: Nic Cope <nicc@rk0n.org>
I'm not exactly sure how this is going to work. My gut feeling is the
easiest thing to do will be for each SDK to have its own copy of the
run_function.proto file, with the 'authoritative' copy being the one
from c/c.
Signed-off-by: Nic Cope <nicc@rk0n.org>