SmbShare: If the Share exists but with the wrong Path, the resource does not update the path

[johlju]

Details of the scenario you tried and the problem that is occurring

This originated from dsccommunity/xSmbShare#10 and was moved here when the module xSmbShare was deprecated.

If the Share exists and the Path is not consistent with the desired state, the resource does not update the path.

Verbose logs showing the problem

Not available.

Suggested solution to the issue

The path cannot be updated without recreating the share, since Set-SmbShare do not support the parameter Path, and New-SmbShare does. Recreating the share could potentially remove configuration that has not been enforced by the DSC configuration. We should support recreating the share, but only if the user expressively allow that by using, for example, a resource parameter Force.

The DSC configuration that is used to reproduce the issue (as detailed as possible)

Any configuration where the desired path mismatch the actual path.

The operating system the target node is running

n/a

Version and build of PowerShell the target node is running

n/a

Version of the DSC module that was used ('dev' if using current dev branch)

dev