(SCHEMA) Update schemas for v3.1.0 release #890
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaeltlombardi
force-pushed
the
schema/main/v3.1.0
branch
from
828ae59 to
bd559a5
Compare
SteveL-MSFT
reviewed
Jun 26, 2025
SteveL-MSFT
requested changes
Jun 26, 2025
theJasonHelmick
approved these changes
Jun 26, 2025
3 tasks
michaeltlombardi
force-pushed
the
schema/main/v3.1.0
branch
from
bd559a5 to
aa026b9
Compare
SteveL-MSFT
previously requested changes
Jun 27, 2025
michaeltlombardi
force-pushed
the
schema/main/v3.1.0
branch
2 times, most recently
from
3858b85 to
b886290
Compare
Prior to this change, the requirements for various resource kinds was incomplete and inaccurate. This change updates the `allOf` applicator to correctly define required and forbidden properties for each resource kind.
Prior to this change, the pattern for fully qualified type names specified that a type name required an owner and supported up to two namespace segments, separated by a period (`.`). This change: - Loosens the pattern by allowing a third segment for subareas. - Updates the in-schema documentation to reflect the change. - Fixes PowerShell#915
Prior to this change, the schema source always expected an embedded schema referencing a canonical property to use the current version. It also didn't support using the shortened form. This change converts the constant for the restriction to point to the valid versions of the schema.
Prior to this change, the extension schemas were erroneously placed in the `extensions` folder instead of the `extension` folder. The schema for the output from `dsc extension list` was missing as was the schema for extension capabilities. This change renames the folder and adds the missing schemas.
michaeltlombardi
force-pushed
the
schema/main/v3.1.0
branch
from
b886290 to
8724b76
Compare
This change makes minor adjustment to the build script for the canonical schemas to capture the new extension schemas. It also updates the configuration to bundle the extension schemas and the stdout schemas.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This changeset includes:
v3.0.1andv3.0.2releases. Neither of these releases required any schema changes except to extend the sets of valid schema URIs for resource manifests and configuration documents.v3.1.0release. This release required changes to support the addition of theexporterresource kind (and associated required output for the Export operation) and the addition of the extension manifest and expected output for the Discover extension operation.Until the changes for v3.1.0 are reviewed, I haven't regenerated the schemas to reduce the noise in the commits. After those changes are reviewed, I'll regenerate the schemas for v3.1.0.
PR Context