microsoft
Microsoft.Winget.DSC/ApplyConfiguration - Nested Configurations
Description of the new feature / enhancement
There are times where it would be nice to create a partial configuration file for a project. For example - I could have a configuration file that only manages the configuration of VSCode, a configuration file that manages Git, a configuration file that manages my WinGet settings, etc.
In order to apply all of these, I would have to call each one separately. It would be useful to be able to be able to write a DSC file that can apply other DSC files.
This would also allow DSC files with many many configuration steps to be broken down into logical parts and re-assembled with a top-level DSC file that applies each of the parts.
Proposed technical implementation details
As a user, I would like to be able to have a DSC file that can apply other DSC files.
There are items that would need to be considered -
- Preventing infinite loops (DSC files calling each other)
- Conflicting states between files
Similar ask on the Dev Home repo https://github.com/microsoft/devhome/issues/3017
being able to include configurations also would help with e.g CI vs regular dev scenarios and updates vs from-scratch setups. using parameters to enable/disable different parts of a configuration using parameters would be another way to avoid lots of duplication ( https://github.com/microsoft/winget-cli/issues/5049 )
