-
Notifications
You must be signed in to change notification settings - Fork 29
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
Enable group resource output schema to simplify config output that uses groups #318
Conversation
fd6ce62
to
9fb3058
Compare
type: Test/Echo | ||
properties: | ||
output: Last | ||
dependsOn: |
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.
seems like too short ident for dependsOn
.
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.
This dependsOn
is for the Last Group
whereas the lines above are the resources within the group, so the indent here is correct
@@ -7,14 +7,17 @@ | |||
"executable": "dsc", | |||
"args": [ | |||
"config", | |||
"test" | |||
"--as-group", |
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.
It would help if there were short examples of format for both --as-group
and --as-get
in PR description (and docs).
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 provided descriptions of those two switches in the PR description. They won't be doc'd since they are hidden and intended to be only used by dsc itself.
@@ -102,6 +147,27 @@ pub struct ResourceTestResult { | |||
pub result: TestResult, | |||
} | |||
|
|||
#[derive(Debug, Clone, PartialEq, Deserialize, Serialize, JsonSchema)] | |||
#[serde(deny_unknown_fields)] |
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 a strong reason to deny_unknown_fields ?
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.
We can evaluate if we want to allow arbitrary fields later if a scenario comes up
PR Summary
get
,set
, andtest
dsc
as a resource has new--as-group
to use this new schemadsc
as a resource has new--as-get
to use with AssertionGroup so that atest
operation still returns aget
output to conform with new schemavalidate
method for group resources instead of relying only on schemadsc
was the resource)osinfo
readme to match codePR Context
Addresses the
get
part of #266,set
andtest
will be addressed in separate PRs