Parameter unknown property

[ThomasNieto]

Summary of the new feature / enhancement

Currently DSC validates that a parameter or parameter file only has properties the config doc has. For example, if I have a parameter file with foo and bar but the config doc only has foo listed as a parameter, dsc will fail during validation. This request is to have a configurable value in the config doc to allow unknown parameters.

As a user I want this file so I can have a single parameter file being passed to multiple config docs.

Proposed technical implementation details (optional)

No response

[michaeltlombardi]

I would propose:

1. We formalize the current behavior as a DSC default setting.

2. We support overriding the default behavior in the DSC settings file, at the CLI, and as an in-document directive.

3. In the initial implementation, overriding the current behavior is not granular. That is, you either error on any unused parameters or ignore every unused parameter in the overriding context. You can't ignore only a subset of unused parameters in the file.

   If we do decide to support more granular overrides, that should be written up as an enhancement feature. It introduces a lot of complexity for static analysis / preflight checks that I'm not sure is justified by the flexibility.