-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update configuration environment behavior #5182
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
Conversation
/// </summary> | ||
/// <param name="set">The set to output.</param> | ||
/// <returns>The string.</returns> | ||
public static string ToYaml(this ValueSet set) |
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 saw this is only used in tests. Is it expected to be used in product code in the future? If not, shall we move the code to test common?
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 honestly didn't notice that this was in the processor; I just assumed that it was in the unit tests as that is how I navigated there (via F12 from a test).
@@ -432,6 +432,11 @@ namespace Microsoft.Management.Configuration | |||
|
|||
[contract(Microsoft.Management.Configuration.Contract, 3)] | |||
{ | |||
// The environment in which to process the configuration set. |
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.
How is the configuration contract version defined? Is it tied to the schema version? (i.e. not tied to our releases since it's still in preview only?)
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 don't have a strict contract number mapping to anything outside of the interface definition.
## Change In response to some other discussions, update the configuration environment behavior: 1. Add an environment at the set level 2. Don't inherit environment data into child units, and don't promote environment data when serializing Updated the one consumer of environment (dynamic factory) to be responsible for the flow of the security context from the set to the immediate child units. Also improved serialization of groups to output the non-resource properties.
Change
In response to some other discussions, update the configuration environment behavior:
Updated the one consumer of environment (dynamic factory) to be responsible for the flow of the security context from the set to the immediate child units.
Also improved serialization of groups to output the non-resource properties.
Microsoft Reviewers: Open in CodeFlow