You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with/fresh will mark this issue as not stale.
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
andresolution
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:
The text was updated successfully, but these errors were encountered: