Winget configure does not support 'architecture'

[novinxy]

Relevant area(s)

WinGet CLI, DSC Resource

Description of the new feature / enhancement

Hi,

I wanted to execute following winget configuration file:

properties:
  configurationVersion: 0.1.0
  resources:
    - resource: WinGetPackage
      id: DotNet 8 (x86)
      settings:
        id: Microsoft.DotNet.Runtime.8
        source: winget
        useLatest: true
        architecture: x86

    - resource: WinGetPackage
      id: DotNet 8 (x64)
      settings:
        id: Microsoft.DotNet.Runtime.8
        source: winget
        useLatest: true
        architecture: x64

In theory it should install .net runtime 8 for both x86 and x64 architecture
But it turns out that architecture is not supported by DSC

winget configure .\configure.winget --accept-configuration-agreements

...
WinGetPackage [DotNet 8 (x86)]
  The configuration unit failed while attempting to test the current system state.
The property 'architecture' cannot be found on this object. Verify that the property exists and can be set.
<See the log file for additional details>
WinGetPackage [DotNet 8 (x64)]
  The configuration unit failed while attempting to test the current system state.
The property 'architecture' cannot be found on this object. Verify that the property exists and can be set.
<See the log file for additional details>
Some of the configuration was not applied successfully.

Proposed technical implementation details

I would love if Microsoft.WinGet.DSC ad architecture option that will enable to specify architecture to choose
I think winget DSC should allow people to configure architecture.

It will enable far wider use of both winget configure and using Microsoft.WinGet.DSC to configure machines.

[mdanish-kh]

yep, that is part of the work being tracked in

• [DSC Resource] Expose more settings to Microsoft.WinGet/Packages #3401

[microsoft-github-policy-service]

Hello @@novinxy,

We've identified this as a duplicate of another issue or PR that already exists. This specific instance is being closed in favor of the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your contribution!

Template: msftbot/duplicate/closed