sparse-intern-71089
08/13/2019, 4:01 PMbest-xylophone-83824
08/13/2019, 4:19 PMorange-policeman-59119
08/13/2019, 4:33 PMgorgeous-egg-16927
08/13/2019, 4:57 PM.get()
operation should fail if the resource doesn’t exist, but doesn’t seem to be the case (it just no-op’d). I’ll check with the team to see if that’s a bugbest-xylophone-83824
08/13/2019, 5:00 PM/api
to get a list of registered apiversions, all installed CRDs are also theregorgeous-egg-16927
08/13/2019, 5:02 PMorange-policeman-59119
08/13/2019, 5:03 PMgorgeous-egg-16927
08/13/2019, 5:03 PMorange-policeman-59119
08/13/2019, 5:04 PMbest-xylophone-83824
08/13/2019, 5:04 PMorange-policeman-59119
08/13/2019, 5:06 PMwhite-balloon-205
Based on the bug report, it looks like the intent is to throw an error if the resource doesn't exist, but the current behavior is my desired behaviorCurious to understand this better. The current behaviour doesn't raise an error - but also doesn't communicate the failure in any generally discoverable way (as well as violating the typing that is promised). If this did throw an error, you could
try/catch
it to do your work in cases where it is not available. Would that accomplish your needs?orange-policeman-59119
08/13/2019, 5:27 PMorange-policeman-59119
08/13/2019, 5:28 PMwhite-balloon-205
| undefined
- but I think the ergonomics of that are actually possible more awkward for normal usage?orange-policeman-59119
08/13/2019, 5:29 PMorange-policeman-59119
08/13/2019, 5:29 PMorange-policeman-59119
08/13/2019, 5:30 PM| undefined
. Also, is the .get
call synchronous? I'm not sure how that works