Failure to parse a single resource.json should Not abort resource enumeration about dsc HOT 4 CLOSED

I was debating on this. We could have a non-terminating error type message, but this error should only ever be encountered by the developer and not the end user so for them it makes sense to just terminate.

from dsc.

Unless the developer distributes a buggy resource?

No resource should be able to disrupt other resources, IMHO. That's not quite what's going on technically, but it is to the user.

from dsc.

My naive expectation would be for dsc resource list to write valid resources to the user and report on discovered but invalid resources on stderr and to return a terminating error when an invalid resource is specified in the dsc config * and dsc resource (get|set|test) subcommands. I don't want dsc config to do anything if one of my specified resources is invalid, because that risks me having a very broken model of the state or configuring a machine haphazardly.

from dsc.

Fixed

from dsc.