Skip to content

(DOCS) Add reference docs for expected resource operations stdout #1016

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

michaeltlombardi
Copy link
Collaborator

PR Summary

This change adds reference documentation for the expected output for the resource operations. It also makes minor corrections to existing reference documentation and extracts the documentation for resource capabilities into a separate file to match the canonical schema.

PR Context

Documenting the expected stdout should help resource authors better understand how to implement and validate their resource design.

Prior to this change, the reference documentation for the `kind`
property of a resource was only partially updated to reflect the
newly available kinds. This change corrects the documentation
to reflect the available kinds.
Prior to this change, the resource capabilities documentation was
only defined in the output for the `dsc resource list` command
reference. This change extracts the useful information into a
separate document, reflecting also the shared definition schema
added in the last release. This supports referencing the schema
from other schemas.

A future change will address updating those reference documents
as needed.
This change updates the `dsc resource list` output reference and
the manifest root reference to reflect the updates to `kind` and
`capabilities`.
This change adds documentation for the `stdout` JSON Schemas indicating how
DSC validates the expected output for the resource operations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants