Closed zzxwill closed 3 years ago
I think this issue is asking for errors pertaining to a managed resource to be surfaced to its resource claim. The resource class based style of resource claim this relates to was deprecated before Crossplane v1.0. Arguably this issue is still relevant to composite resources and composite resource claims, which do not currently aggregate every error that a composed resource surfaces. I'm going to close this issue and encourage you to raise a similar one for composite resources and composite resource claims under crossplane/crossplane if you feel it's still relevant.
What happened?
Followed
README.md
to make a PoC, I accidentally export Alibaba Cloud ACCESS_KEY_ID with wrong value, it hit the issueManaged resource is not yet bindable
, which doesn't sounds useful to me, and it took me a while to locate the root cause. It would be better if it could raise error message from Cloud provider provisioning Cloud resource, likeSpecified access key is not valid
How can we reproduce it?
Followed provider-alibaba README and export wrong access-key information.
What environment did it happen in?
Crossplane version: