You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to capture all Windows Settings as DSC Resources.
Microsoft.Windows.Setting would be the "top level" module so all the children could be included for WinGet to be able to winget configure export.
This list below is organized based on appearance in Windows Settings (Windows 11).
I'll update the description as we continue to break things out. I just wanted to get this issue in place to help track the work as we coordinate with other collaborators.
Note: This module is in development, and in its current implementation it would generate a large number of entries in the configuration file. We're considering the concept of "export not default" which would essentially only generate lines of configuration for settings that were not in their default state to reduce the size of the WinGet configuration file.
Proposed technical implementation details
No response
The text was updated successfully, but these errors were encountered:
Description of the new feature / enhancement
I'd like to capture all Windows Settings as DSC Resources.
Microsoft.Windows.Setting would be the "top level" module so all the children could be included for WinGet to be able to
winget configure export
.This list below is organized based on appearance in Windows Settings (Windows 11).
I'll update the description as we continue to break things out. I just wanted to get this issue in place to help track the work as we coordinate with other collaborators.
Note: This module is in development, and in its current implementation it would generate a large number of entries in the configuration file. We're considering the concept of "export not default" which would essentially only generate lines of configuration for settings that were not in their default state to reduce the size of the WinGet configuration file.
Proposed technical implementation details
No response
The text was updated successfully, but these errors were encountered: