Known coming breaking changes

[SteveL-MSFT]

Summary of the new feature / enhancement

• WhatIf arg kind for Set and Delete
  • Remove WhatIf operation and only use arg kind
• Authenticode opt-out
  • Initially unsigned config, resource manifest, and binaries emit warnings will eventually be errors
• Adapters default to single resource inputKind
  • Currently adapters only expect getting a config doc which is getting more complex as the project evolves
• Remove support for validate method for adapters, require adapters to return JSONSchema which is needed for intellisense experience

Proposed technical implementation details (optional)

No response

[ThomasNieto]

• https://github.com/PowerShell/DSC/issues/983

[whindsaks]

And can you bypass the signing requirements with a flag once they turn into errors?

[SteveL-MSFT]

And can you bypass the signing requirements with a flag once they turn into errors?

I would expect we would also have policy settings for enterprise scenarios to restrict turning it off, but it probably makes sense for dev scenarios to have a switch and/or setting to bypass.

[Gijsreyn]

• CLI parameters and subcommands #984

[ThomasNieto]

Can we get a dedicated issue for the Authenticode feature with proposed design? I'd like to know how it's going to work with import feature since those won't be signed.

[SteveL-MSFT]

Can we get a dedicated issue for the Authenticode feature with proposed design? I'd like to know how it's going to work with import feature since those won't be signed.

For the import feature, the importer will be checked if signed, but the contents it imports is the responsibility of the importer to validate it's signed. This is similar problem to adapters. I think what we need is a new ArgKind to indicate to importers and adapters that it needs to validate their content is signed.

Created https://github.com/PowerShell/DSC/issues/1131 for this