Draft resource authoring design guide#372
Draft resource authoring design guide#372michaeltlombardi wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
2f7be55 to
6883779
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This change drafts the conceptual documentation for guidance on how to author DSC resources from a design perspective. It does not include any specific guidance from a code or language perspective. Instead, it focuses on the high level concepts and on defining the resource manifest and instance JSON Schema. This change is a mirror of the one submitted to the source repository: - PowerShell/DSC#1027
6883779 to
b1c7d43
Compare
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit b1c7d43:
|
PR Summary
This change drafts the conceptual documentation for guidance on how to author DSC resources from a
design perspective. It does not include any specific guidance from a code or language perspective.
Instead, it focuses on the high level concepts and on defining the resource manifest and instance JSON Schema.
This change is a mirror of the one submitted to the source repository:
To do:
PR Checklist