How to run `wingetcreate new` non-interactively?

[ldennington]

Discussed in #188

Creating an issue for visibility.

^{Originally posted by ldennington October 14, 2021}
Hello,

I'm reaching out because I'm interested in using wingetcreate in my GitHub Actions workflows to publish packages my team owns to winget. We are currently using a custom task (see example here), which has been a pain point since the manifest specification changes frequently.

In light of this, I'm reaching out to see whether it's possible to run wingetcreate new non-interactively. Whenever I run any of the following locally, I'm prompted to manually accept/override the default values from my installer:

wingetcreate new https://github.com/ldennington/Git-Credential-Manager-Core/releases/download/winget_test/gcmcore-win-x86-2.0.559.38027.exe --out manifests --token <insert-token-here>

wingetcreate new https://github.com/ldennington/Git-Credential-Manager-Core/releases/download/winget_test/gcmcore-win-x86-2.0.559.38027.exe

I see the example shows the wingetcreate update command in a pipeline, but not wingetcreate new, which prompted me to ask this question.

[jedieaston]

I don't think it's possible ATM. There's too much metadata that needs to be filled out (privacy policy, website, localized names, etc). wingetcreate new is designed to be ran only once for an application, whereas wingetcreate update is designed to be ran for every new version of an app (where it copies most of the values asked for during new from the previous version), as such, it's acceptable that it's not automated (or at least, it has been up to this point).

What's the usecase where you want to automate wingetcreate new? For the example action you linked, right now that could be replicated by the command wingetcreate update -u {{url}} -v {{version}} Microsoft.GitCredentialManagerCore (and if you want to submit, add the --submit --token <TOKEN> arguments to that).