-
Notifications
You must be signed in to change notification settings - Fork 49
(DOCS) Scaffold resource authoring docs #1027
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
(DOCS) Scaffold resource authoring docs #1027
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good starting structure.
I recall seeing it mentioned in the documentation you wrote earlier, Mikey, but after our discussion yesterday, would it be worth pointing out a naming convention for a new DSC resource? |
This change adds conceptual documentation as the initial offering for a resource _design_ guide. It is intended to convey high-level implementation-agnostic guidance for defining DSC resources, including resource manifests and instance schemas. The guide doesn't cover any specifics for defining commands or the resource in a particular language. Those concerns are better covered in the resource development kits or the sample resource tutorials, not the conceptual guide.
012258b
to
fea6566
Compare
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
Users can configure the trace level for DSC by specifying the | ||
[--trace-level](../../../reference/cli/index.md#--trace-level) command option, setting the | ||
[DSC_TRACE_LEVEL](../../../reference/cli/index.md#environment-variables) environmental variable, or | ||
by modifying the settings for DSC. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might have already seen it, but maybe you can reference the settings to the docs when it gets pulled in (#1044)?
When a user specifies the [--trace-format](../../../reference/cli/index.md#--trace-format) option | ||
as `plaintext`, DSC emits the messages in the same format but without console colors. | ||
|
||
When a user specifies the format as `json`, DSC emits each message as a JSON Line to stderr. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Perhaps make a reference towards: https://jsonlines.org/
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
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
PR Summary
This change adds empty documents to suggest the structure and content of a resource authoring guide.
It is intended to convey high-level design guidance and implementation-agnostic guidance for authoring resource manifests and instance schemas.
It doesn't cover any specifics for defining commands or the resource in a particular language. Those concerns are better covered in the resource development kits or the sample resource tutorials, not the conceptual guide.
PR Context
A recurring ask from partners and community members is how to begin authoring a DSC resource. This high-level guide will provide a starting point for such development.