WinGet Export can generate a WinGet Configuration File

[denelon]

Description of the new feature / enhancement

I'd like to have winget export build a WinGet Configuration file to install my packages.

This will help with users who want to run WinGet Configure so they don't have to manually convert a packages.json file into a configuration.dsc.yaml file.

We're also thinking about:

• WinGet Import acts as an alias for WinGet Configure #4093

Note: This is not the same as:

• Generate configuration from machine state  #3274

Proposed technical implementation details

If I run winget export --configuration configuration.dsc.yaml WinGet generates a configuration file.

[SamHasler]

is this a duplicate of (or otherwise fulfils the requirements of) #3555 ?

[denelon]

@SamHasler, No,

• Convert packages.json (WinGet Export) to configuration.dsc.yaml (Configuration file) #3555
  is just a utility concept to convert some packages.json file over into a WinGet configuration file for some point in the future where we no longer want WinGet to need to support two different syntaxes for installing a set of packages.

I haven't decided on the implementation details, but I'll share some thinking below.

As we work towards:

• Generate configuration from machine state  #3274

I want to somewhat standardize the behaviors of WinGet with respect to the existing "import" and "export" commands.

My thought process is we need to implement:

1. WinGet Import acts as an alias for WinGet Configure #4093
2. WinGet Export can generate a WinGet Configuration File #4092 <-This might be limited to the current "packages only" scenario initially.

I'm just mostly concerned about some confusion that may arise out of the nuanced differences between a winget configure export and a winget export as well as the current behavior for winget import and winget configure.