ADReplicationSiteLink: Verbose message does not show a current value when missing current value #519
Labels
enhancement
The issue is an enhancement request.
good first issue
The issue should be easier to fix and can be taken up by a beginner to learn to contribute on GitHub
Details of the scenario you tried and the problem that is occurring
If the current value is not set (empty or null) the verbose message does not show a current value when testing the configuration.
Verbose logs showing the problem
Suggested solution to the issue
This could be enhanced to handle
$null
values to get a more descriptive verbose message.The DSC configuration that is used to reproduce the issue (as detailed as possible)
The existing integration test can be used to see and resolve this issue. Snippet from the integration tests below.
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
The text was updated successfully, but these errors were encountered: