Add known issue with Windows PowerShell adapter and example fix #1094
+40
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
PSDesiredStateConfiguration v2.0.7 doesn't have this issue. |
docs/troubleshooting/known-issues.md
Outdated
|
|
||
| When running `dsc resource list --adapter Microsoft.Windows/WindowsPowerShell`, you | ||
| may see zero resources returned. In trace or debug logs, an error like the following can | ||
| appear: "Cannot bind argument to parameter 'Path' because it is an empty string." |
There was a problem hiding this comment.
Suggested change
| appear: "Cannot bind argument to parameter 'Path' because it is an empty string." | |
| appear: | |
| ```console | |
| Cannot bind argument to parameter 'Path' because it is an empty string. | |
| ``` |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This pull request adds a known issue when running
dsc resource list --adapter Microsoft.Windows/WindowsPowerShellwith the$env:PSModulePathcontaining a ";" at the end. It also fixes up an example, which was reported on the dsc channel (Discord).PR Context