-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Dscv3 package resource #5395
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
Dscv3 package resource #5395
Conversation
<value>Indicates whether to accept agreements for package installs.</value> | ||
</data> | ||
<data name="CorrelationArgumentDescription" xml:space="preserve"> | ||
<value>An unused argument for logging</value> |
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 this intended to be in product code?
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 did consider making it test specific, but it seems reasonable to allow it to be passed in by anyone so that log files can be tagged.
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.
nit: maybe a description like "hidden argument" would be better than "unused"
{ | ||
return MatchType::Exact; | ||
} | ||
else if (lowerValue == "equals""case""insensitive") |
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 it for preventing spelling check errors?
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.
Yes, the spell checker is ok with this and C rules means that this is the same as "equalscaseinsensitive"
.
|
||
if (package.Scope != Manifest::ScopeEnum::Unknown) | ||
{ | ||
output.Scope(ConvertScope(Manifest::ScopeToString(package.Scope), true)); |
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.
If we export Scope, during apply, will it be enforced during installer selection and may cause failures? i.e. we have many installers that do not specify scope.
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.
Good point; I think we would need to support the "OrUnknown" variants for this to work as simply as it is now. Alternately, we would need to check that the current scope is an available installer or track scope intent as we do for some other values.
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.
Yeah, the other thing (for export) besides scope that could be a challenge is the install location.
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.
Change
Add a new DSC v3 resource:
package
. This largely follows the design of the v2 resource, but uses the v3 paradigm for existence.Other minor changes:
StdErrLogger
and attaches it during resource execution. This currently writes all logs atError
or higher tostd::cerr
, allowingdsc.exe
to receive (and pass on) failure information.ManifestComparator
to common for re-use.Validation
Added E2E tests to invoke the package resource in a variety of situations.
Microsoft Reviewers: Open in CodeFlow