You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, add-credentials always asks credentials from the console.
In our developer machine setup, we automatically configure configuration files for various build systems / tools like maven, gradle, npm, nuget all using the same user credentials.
We do this by reading the credentials from the user once and after that executing config commands of the tools in sequence (npm config auth, nuget source...)
However, Paket does not allow to specify username and password directly on the command line, which makes it a lot harder to automatically configure it using that system.
Yes this sounds doable.
I'm making this up-for-grabs
On Jun 14, 2016 15:35, "Stephan Pauxberger" [email protected]
wrote:
Currently, add-credentials always asks credentials from the console.
In our buildsetup, we automatically configure configuration files for
various build systems / tools like maven, gradle, npm, nuget all using the
same user credentials.
We do this by reading the credentials from the user once and after that
executing config commands of the tools in sequence (npm config auth, nuget
source...)
However, Paket does not allow to specify username and password directly on
the command line, which makes it a lot harder to automatically configure it
using that system.
Currently, add-credentials always asks credentials from the console.
In our developer machine setup, we automatically configure configuration files for various build systems / tools like maven, gradle, npm, nuget all using the same user credentials.
We do this by reading the credentials from the user once and after that executing config commands of the tools in sequence (npm config auth, nuget source...)
However, Paket does not allow to specify username and password directly on the command line, which makes it a lot harder to automatically configure it using that system.
I suggest providing a --batch flag:
paket config add-credentials --batch
alternatively:
paket config add-credentials --username --password
The text was updated successfully, but these errors were encountered: