NI Package Manager (NIPM)
Authentication/Proxy for NIPM (nipkg.exe)
I'm currently playing around with the --proxy and --proxy-user settings for nipkg.exe, in relation to questions like Oli's here: https://forums.ni.com/t5/NI-Package-Manager-NIPM/Feed-URL-gt-how-does-NIPM-handle-user-credentials/t...
(i.e. because you can't currently use authentication parameters anywhere else than for the proxy server).
I have a few questions (numbered in the hope of a reply with reference, rather than by order or importance):
- Why do both `feed-add` and `feed-update` have proxy parameters? (Are the values passed to feed-add stored for that feed? If I run nipkg.exe feed-update my_proxied_feed after using the params for feed-add --name "my_proxied_feed" --proxy="http://blah.com:<port>" --proxy-user="cbutcher:password" "http://mypackagehost.com/package-repo", should I expect the proxy values to be used?
- Are there other settings that control if/when the proxy values are used? (in particular, does NIPM confirm the 'remoteness' of a URL before attempting to use a proxy? Or attempt to hit it directly first, then fall back to the proxy?)
- Is there a timeline for adding auth options to the feeds without considering proxies?
- Will NIPM warn me if I pass values that don't match its expectations? (This seems to be not the case, but perhaps it allows a wide range of inputs). In particular, are things like `--proxy="http://hostname:port/some/trailing/path" (or http://hostname.com/path/to/route:port) allowed? (I recognise this is not a typical proxy argument, and further that the nipkg.exe help lists "[<protocol>://]proxyhost[:<port>]"
