The Microsoft.WinGet.RestSource PowerShell module is provided for creating and managing Windows Package Manager REST sources.

Please visit Create a Windows Package Manager REST source for more details.

• Git Large File Storage (LFS)
• Visual Studio 2022
• The following workloads:
  • .NET desktop development
  • Azure development
  • ASP.NET and web development

Open src\WinGet.RestSource.sln in Visual Studio and build. We currently only build using the solution; command line methods of building a VS solution should work as well.

The REST functions can be run locally, but to use winget with them, the functions must be run using HTTPS. This is pre-configured by the launchSettings.json file.

1. In the src\WinGet.RestSource.Functions directory, run generate_self_sign_cert.ps1 in PowerShell.
   • This will generate a test pfx and install it into the Root store.
   • It will automatically be used as the HTTPS cert during local execution, thanks to launchSettings.json
2. Create a CosmosDB database instance in Azure, using either the above instructions, or manually.
   • Navigate to the Keys section of your CosmosDB instance in the Azure portal to find your connection information.
   • If you've used the ARM templates as described above, your Database will be named WinGet and your Collection will be Manifests
3. Copy src\WinGet.RestSource.Functions\local.settings.template.json to local.settings.json and populate required fields from the above Keys section.
4. In source codes, change HttpTrigger level to Anonymous for InformationGet, ManifestSearchPost and ManifestGet endpoints.
5. Run the WinGet.RestSource.Functions project locally in Visual Studio using F5.
6. Add it as a source in winget with: winget source add -n "winget-pkgs-restsource" -a https://localhost:7071/api/ -t "Microsoft.Rest"

Your commands to winget will now use your locally running REST instance as a user added source.

Running tests are a great way to ensure that functionality is preserved across major changes. You can run these tests in Visual Studio Test Explorer. In Visual Studio, run the tests from the menu with Test > Run All Tests

• Install the Cosmos DB Emulator
• Copy the WinGet.RestSource.UnitTest\Test.runsettings.template.json template configuration to Test.runsettings.json
  • The defaults should work for your local Cosmos DB emulator instance. You can change the configuration to point to a Cosmos DB instance in Azure instead.
  • Alternatively, all of the test configuration properties can be set as environment variables. This is useful for overriding properties in an ADO build.

• Install the winget client locally.
• Copy the WinGet.RestSource.IntegrationTest\Test.runsettings.template.json template configuration to Test.runsettings.json
  • Modify the RestSourceUrl property to point to a deployed REST source endpoint. You can use the below instructions to deploy a REST instance.
  • If the local winget client doesn't already have the source added, the integration tests can add it. To do so, change the AddRestSource property to true. Visual Studio must be running as admin in this case.
  • There is a test case that modifies the REST source. This test is disabled by default. To run it the RunWriteTests setting must be set to true. The FunctionsHostKey setting must also be set since the add/update/delete endpoints all require function authorization. We recommend creating a new pipeline-specific host key for this purpose.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.