Include existing apps into Machine Configuration

[pkbullock]

Suggested new feature or improvement

If building on a machine already setup, create configuration files based on existing setup.

Scenario

If building on a machine already setup, create configuration files in order to use on another machines, like treating the existing machine as a template. DevHome assumes a blank machine to start with, true to applying a configuration, but authoring, developers may want an existing machine to capture the configuration.

Additional details

No response

[AllanMiller-MSFT]

This may be possible with a limited scope, for example current winget items installed. Even just winget installed would require all package metadata to be known to check. Then other scopes like Windows Features. GPO has the same limit where you can only determine based on the current local templates available.
First thing I wanted as well.

[AmelBawa-msft]

Possibility covered by this issue? #721

[pkbullock]

Hi @AllanMiller-MSFT and @AmelBawa-msft, this might be a UX issue, from the screen when I am building the configuration, under the end-to-end setup, I thought this was an authoring option for a configuration file, rather than just installed the apps and clone repositories. It does appear related to #721 as a to export config, I'm kind of talking about a 3rd option to create a configuration file but with a UI like with the end-to-end setup, selecting the repos and apps, then it creates the file. for later reuse.

There are going to be quite a few devs that have already setup their environments so way to capture and create the Yaml file would be awesome.