What happened?
https://github.com/upbound/provider-aws/blob/6075caef/package/crds/aws.upbound.io_providerconfigusages.yaml#L52
We added these new fields in #328. I believe the intention was to affect only cross-resource references. Unfortunately the PR added the fields to generic reference types that are used in many places in Crossplane - for example in the ProviderConfigUsage above.
I believe this means we now have a few reference fields in Crossplane that expose resolve and resolution fields that don't actually do anything. This is a poor user experience - since anyone looking at the API docs might find them and think they can use them.
I would suggest we either:
- Remove these fields where they're not used.
- Make sure they work everywhere that they exist.
What happened?
https://github.com/upbound/provider-aws/blob/6075caef/package/crds/aws.upbound.io_providerconfigusages.yaml#L52
We added these new fields in #328. I believe the intention was to affect only cross-resource references. Unfortunately the PR added the fields to generic reference types that are used in many places in Crossplane - for example in the
ProviderConfigUsageabove.I believe this means we now have a few reference fields in Crossplane that expose
resolveandresolutionfields that don't actually do anything. This is a poor user experience - since anyone looking at the API docs might find them and think they can use them.I would suggest we either: