Configuration for the SDK currently supports providing a CliPath. While this is representative of the current architecture, it's not necessarily the only way things could be deployed, e.g. the full implementation could be embedded as a library in the calling process. We should ensure the shape and naming of such properties / functionality doesn't constrain future evolution.
Configuration for the SDK currently supports providing a CliPath. While this is representative of the current architecture, it's not necessarily the only way things could be deployed, e.g. the full implementation could be embedded as a library in the calling process. We should ensure the shape and naming of such properties / functionality doesn't constrain future evolution.