Details of the scenario you tried and the problem that is occurring
Create a new Guest Configuration Package by using New-GuestConfigurationPackage and use a whitespace in the name. Package will not be able to report back the result of the assignment report using the url (sample: https://westeurope-gas.guestconfiguration.azure.com/virtualMachines//assignments//reports?api-version=2020-11-08)
Verbose logs showing the problem
None
Suggested solution to the issue
The name would need to be Url Encoded (%20) either this should be implemented into the (/home/dscbuilder/DesiredStateConfiguration/src/dsc/gc_pullclient/dsc_pull_client.cpp:388 - reporting the error) or New-GuestConfigurationPackage should validate that no unsupported Characters are part of the name (Tooling Support).
The DSC configuration that is used to reproduce the issue (if applicable)
Any
The operating system the target node is running
Linux, Windows
Version and build of PowerShell the target node is running
Details of the scenario you tried and the problem that is occurring
Create a new Guest Configuration Package by using New-GuestConfigurationPackage and use a whitespace in the name. Package will not be able to report back the result of the assignment report using the url (sample: https://westeurope-gas.guestconfiguration.azure.com/virtualMachines//assignments//reports?api-version=2020-11-08)
Verbose logs showing the problem
None
Suggested solution to the issue
The name would need to be Url Encoded (%20) either this should be implemented into the (/home/dscbuilder/DesiredStateConfiguration/src/dsc/gc_pullclient/dsc_pull_client.cpp:388 - reporting the error) or New-GuestConfigurationPackage should validate that no unsupported Characters are part of the name (Tooling Support).
The DSC configuration that is used to reproduce the issue (if applicable)
Any
The operating system the target node is running
Linux, Windows
Version and build of PowerShell the target node is running
7.1
Version of the module that was used
3.4.2