You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current resource WSManServiceConfig only configures settings in the wsman:\localhost\service* path. We should create a new resource that manages the items in the Wsman:\localhost* path called WSManConfig.
This would also imply a resource should be created called WSManClientConfig and WSManShellConfig.
These new resources would be copied from WSManServiceConfig with the data files changed. Although combining these properties into the existing WSManServiceConfig would be a simple approach too (with some modification) it would result in the name needing to be changed to correctly indicate the purpose of the resource - which would result in a breaking change.
So implementing multiple resources seems to be the best approach.
The current resource WSManServiceConfig only configures settings in the wsman:\localhost\service* path. We should create a new resource that manages the items in the Wsman:\localhost* path called WSManConfig.
This would also imply a resource should be created called WSManClientConfig and WSManShellConfig.
These new resources would be copied from WSManServiceConfig with the data files changed. Although combining these properties into the existing WSManServiceConfig would be a simple approach too (with some modification) it would result in the name needing to be changed to correctly indicate the purpose of the resource - which would result in a breaking change.
So implementing multiple resources seems to be the best approach.
See https://github.com/PlagueHO/WSManDsc/issues/2#issuecomment-532773432
Tagging @fullenw1
@johlju - any thoughts on this one?
The text was updated successfully, but these errors were encountered: