Nic Cope
Here's a strawman sketch of what generic cross-resource references might look like. Today we have this for example: ```yaml --- apiVersion: network.aws.crossplane.io/v1alpha2 kind: VPC metadata: name: my-vpc spec: ... ---...
Unstale please. I'm still pretty sure we're going to need this.
Throwing out another idea (based on a demo of something related @apelisse put together) - I could see a distinct `Reference` type being in some ways better than an array...
I was just reminded of one other shortcoming with generic references - when any field can be 'computed' by a reference no field can be required in the OpenAPI schema...
> when any field can be 'computed' by a reference no field can be required in the OpenAPI schema sense Last night I was wondering whether a mutating admission control...
xref to https://github.com/crossplane/crossplane/issues/2499, which was somewhat similar.
I wouldn't _normally_ be a fan of sharing the same structs across API types due to the strong coupling of APIs. That is, if we ever did want to change...
FWIW with that in mind my preference is to use a code generator to automatically copy types. Bonus points if it's generally applicable - i.e. for next time we're in...
> What if there are breaking changes in the Composition API in the future? How does Crossplane switch between pre- and post-breaking revisions? The Composition API is v1, so we...
@muvaf I just took a look and don't see `release-1.10` so I'm guessing someone else beat me to it.