-
Notifications
You must be signed in to change notification settings - Fork 263
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update schema for draft 2020-12 compliance (#851)
* Make schema draft 2020-12 compliant * Make schema draft 2020-12 compliant * additional fixes
- Loading branch information
Showing
6 changed files
with
689 additions
and
756 deletions.
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
6fd76db
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.
Is there somewhere else that these schemas are being pulled from? I notice some small things the schema doesn't define like a lot of the properties under metadata, so if you're performing scripted/automated updates of your policies based on these schemas, then you get a lot of properties swapping around, creating unnecessary changes in the code.
I'd be open to updating some of the schemas myself through a pull request since I'm interested in making these modifications even just for myself, but it'd be good to know prior if there's a reason some of these properties were not included initially or even in subsequent updates like this one or if they're just being programically produced from another source.