Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New-WinGetSource fails with Unauthorized error on publish-azwebapp

Open
  • Is something wrong?
#234 1 comment 0 reactions 1 assignee View on GitHub

@RDMacLachlan is already working on this.

Since Apr 11, 2024.

Assessment

This issue has not been assessed yet.

Description

Issue-Bug
Brief description of your issue

Attempting to create a New-WinGetSource fails on line 157 of New-ARMObjects.ps1:
$Result = Publish-AzWebApp -ArchivePath $RestSourcePath -ResourceGroupName $AzResourceGroup -Name $AzFunctionName -Force
with error:
..."\WinGet.RestSource-Winget.PowerShell.Source\Library\New-ARMObjects.ps1:157
Line |
157 | … $Result = Publish-AzWebApp -ArchivePath $RestSourcePath -ResourceGr …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Deployment failed with status code Unauthorized"

Steps to reproduce

This command works until the last step of publishing as described above:

New-WinGetSource -Name "contosorestsource4" -ResourceGroup "rg-winget-rest-source" -Region "eastus" -ImplementationPerformance "Basic" -ShowConnectionInstructions -Verbose

I haven't figured out why it is failing but I noticed two things:

  1. a resource group with the same name as the one I gave was also created but without and hyphens. I get this warning for an RG I'm not using: "WARNING: Found an existing Resource Group matching the name of rgwingetrestsource. Will not create a new Resource Group." this seems like a separate bug. If I look in my RGs this new RG does exist and there is nothing inside.

  2. The function app environment variables is missing a few values because their names cannot be found in the key vault. The "New-ARMObjects.ps1" script does not appear to attempt to create these missing key vault secrets with the names expected in the Function App environment variables so I'm not sure why they are mentioned in the Function App config. Screenshot:
    image

Expected behavior

I expected the command to complete successfully

Actual behavior

Failure due to auth

Environment
Windows Package Manager v1.7.10861
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3296
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0
Dominant language
C#
Stars
317
Forks
79
Avg merge
12h 22m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli-restsource

All issues in microsoft/winget-cli-restsource

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.