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
Details of the scenario you tried and the problem that is occurring
Hi, I was trying to run KeyValuePairFile from FileContentDsc on an empty .config file to try to populate some new entries. Not sure if this is supported or not or if I should be using a different DSC resource, but I kept getting errors, I'm assuming because the file was empty and everything the DSC resource was trying to work with was null.
Realistically, for what I'm going to be using this for, I won't be having this issue. Just figured I'd bring it up since I ran into it.
Verbose logs showing the problem
This was in my event viewer for operational DSC logs:
Version of the DSC module that was used ('dev' if using current dev branch)
1.1.0.108
The text was updated successfully, but these errors were encountered:
PlagueHO
added
needs investigation
The issue needs to be investigated by the maintainers or/and the community.
bug
The issue is a bug.
help wanted
The issue is up for grabs for anyone in the community.
and removed
needs investigation
The issue needs to be investigated by the maintainers or/and the community.
labels
Jul 16, 2019
Hi @ActionN - thanks for raising this. It does indeed look like a bug: The resource does not create the file if it does not exist. But it should - so I'll fix this ASAP. I'm snowed under at work for the next two days but I'll try and get to this Thursday night. It should be a fairly straight forward fix, but I'll need to add some integration tests to ensure it's fixed correctly.
Details of the scenario you tried and the problem that is occurring
Hi, I was trying to run KeyValuePairFile from FileContentDsc on an empty .config file to try to populate some new entries. Not sure if this is supported or not or if I should be using a different DSC resource, but I kept getting errors, I'm assuming because the file was empty and everything the DSC resource was trying to work with was null.
Realistically, for what I'm going to be using this for, I won't be having this issue. Just figured I'd bring it up since I ran into it.
Verbose logs showing the problem
This was in my event viewer for operational DSC logs:
Event 4252 -
Job {43432191-A78D-11E9-837E-408D5C58C088} :
MIResult: 1
Error Message: Exception calling "Matches" with "3" argument(s): "Value cannot be null.
Parameter name: input"
Message ID: ArgumentNullException
Error Category: 0
Error Code: 1
Error Type: MI
From Get-DscConfigurationStatus -
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Version and build of PowerShell the target node is running
Name Value
PSVersion 5.1.17763.592
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.592
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version of the DSC module that was used ('dev' if using current dev branch)
1.1.0.108
The text was updated successfully, but these errors were encountered: