ENOENT failure when IC2 runs Salesforce CLI commands

[Scott Wells]

I’m adding this a placeholder for users who might see this issue manifest through IC2, but it’s not an IC2 issue. Here is the corresponding Salesforce CLI issue:

https://github.com/forcedotcom/cli/issues/2209

which is itself part of a larger class of issues relating to the logger used by the CLI:

https://github.com/forcedotcom/cli/labels/logger-replacement

I’ve considered adding a workaround to IC2 to detect and (attempt to) correct the malformed JSON output, but given that Salesforce is actively working on a solution to this, my hope is that a true fix will be available soon enough that a workaround will not be warranted.