Closed anmenaga closed 7 months ago
I'm not sure we should support non-deterministic resource operations, especially for set
. Searching for a resource is less impactful than calling the operation for a resource.
Seems dangerous to allow executing an operation against a wildcard resource. The WG discussed this and don't believe we should support wildcards beyond resource lookup.
Prerequisites
Steps to reproduce
Currently only list operation supports wildcards:
dsc resource list test*
Other operations do not support this currently and end up with 'resource not found' error. Also need to define what that would mean for
get/set/test/...
operations... doing the operation with the same input on all resource types that match the wildcard?Expected behavior
Actual behavior
Error details
No response
Environment data
Version
v1
Visuals
No response