- Notifications
You must be signed in to change notification settings - Fork45
(SCHEMA) Update schemas for v3.1.0 release#890
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
828ae59
tobd559a5
CompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
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.
- Steve's comments - LGTM
bd559a5
toaa026b9
CompareUh oh!
There was an error while loading.Please reload this page.
3858b85
tob886290
CompareThere 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.
LGTM
Prior to this change, the requirements for variousresource kinds was incomplete and inaccurate. Thischange updates the `allOf` applicator to correctlydefine required and forbidden properties for eachresource kind.
Prior to this change, the pattern for fully qualified type namesspecified that a type name required an owner and supported up totwo 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.-FixesPowerShell#915
Prior to this change, the schema source always expected anembedded schema referencing a canonical property to usethe current version. It also didn't support using theshortened form.This change converts the constant for the restriction topoint to the valid versions of the schema.
Prior to this change, the extension schemas wereerroneously placed in the `extensions` folderinstead of the `extension` folder. The schemafor the output from `dsc extension list` wasmissing as was the schema for extensioncapabilities.This change renames the folder and adds themissing schemas.
b886290
to8724b76
CompareThis change makes minor adjustment to the build script for thecanonical schemas to capture the new extension schemas. It alsoupdates the configuration to bundle the extension schemas and thestdout schemas.
9903df4
Uh oh!
There was an error while loading.Please reload this page.
PR Summary
This changeset includes:
v3.0.1
andv3.0.2
releases. 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.0
release. This release required changes to support the addition of theexporter
resource kind (and associated required output for theExport operation) and the addition of the extension manifest and expected output for theDiscover 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