WinGetPackage does not work when source is removed #5144
Labels
Command-Configure
Issue related to WinGet Configuration
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Brief description of your issue
I was playing around with the winget-cli-restsource in combination with the WinGetPackage DSC module and noticed something unexpected.
When I deployed the whole solution and added the source using the winget source add command, everything was working perfectly when I deployed the following:
After finishing up my testing with the private REST source, I deleted the resources in Azure. Here comes the interesting part: the source was, of course, still present, and an attempt to re-apply the configuration started to fail even though the source had been defined in the configuration file:
Of course, after removing the source, it worked again. However, this looks like these rough edge cases.
Steps to reproduce
Microsoft.WinGet.DSC/WinGetPackage
resource targetting winget as sourcePackage aren't able to install.
Expected behavior
Package should be able to install.
Actual behavior
An error occurred while connecting to the catalog.
Environment
The text was updated successfully, but these errors were encountered: