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
When I build a resource using DRG and the description for a parameter contains quotes, these are not replaced or edited meaning that the resulting mof-file is unreadable to DSC.
Verbose logs showing the problem
Suggested solution to the issue
Location in the DRG-module where comments are added to the mof-definition: Lines 721 and 726, $mofSchemaContent.Appendline(... $property.Description)....). Code should be added to ensure the description is edited so quotes are replaced by apostrophes or something similar.
I don't have available time to do a PR myself but thought I'd bring it up.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# insert configuration hereNew-M365DSCResource....
#### The operating system the target node is running#### 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:
Sounds right. I came across it when testing another resource and got an error from DSC complaining about an unrelated resource-schema that turned out to have a field that contained double quotes as part of the description
Details of the scenario you tried and the problem that is occurring
When I build a resource using DRG and the description for a parameter contains quotes, these are not replaced or edited meaning that the resulting mof-file is unreadable to DSC.
Verbose logs showing the problem
Suggested solution to the issue
Location in the DRG-module where comments are added to the mof-definition: Lines 721 and 726, $mofSchemaContent.Appendline(... $property.Description)....). Code should be added to ensure the description is edited so quotes are replaced by apostrophes or something similar.
I don't have available time to do a PR myself but thought I'd bring it up.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The text was updated successfully, but these errors were encountered: