-
Notifications
You must be signed in to change notification settings - Fork 42
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
Move Permissions definition in rockcraft schema to top scope #460
Move Permissions definition in rockcraft schema to top scope #460
Conversation
e394877
to
08e268e
Compare
@cjdcordeiro @tigarmo This should be ready for review. |
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.
I can confirm it works.
For future reference, and possibly automation, is there an easy way to test this?
We can use this github action to validate our schema: |
Do you have an example of it passing & failing with this "Permissions definition" issue? |
I have an example of it failing where it should have succeeded :-) I'm not sure but I think it doesn't support the 2020-12 schema draft. I'm experimenting with alternatives now. |
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.
thanks!
@cjdcordeiro @linostar do we want to do anything else on this PR before merging it?
This should be good to merge, because it provides the needed fix. After discussing with Cris, I'll create another PR that provides automated validation of the generated rockcraft schema. |
This is to fix an issue in Rockcraft's schema.json, because
Permissions
needs to moved to the top scopedefinitions
instead of being located insidePart
's definitions.