On Fri, Dec 11, 2020 at 02:35:01PM +0100, Patrick Steinhardt wrote: > > E.g. IIRC this whole series is because it's a hassle to invoke > > core.askpass in some stateful program where you'd like to just provide a > > transitory password. I think some brief cross-linking or explanation > > somewhere of these various ways to pass sensitive values around would be > > relly helpful. > > It had been the original intention, yes. And it still is, but in fact > the usecase has broadened to also use it to get rid of our global git > config in Gitaly. Which is a little bit awkward to do with > `--config-env` or `-c`, as now a ps(1) would first show a dozen of > configuration values only to have the real command buried somewhere at > the back. It would have been easy to implement though with the > GIT_CONFIG_ envvars. I don't know what kinds of variables you want to set exactly, but another possible option here is some mechanism to point Git to an extra config file. This would work if you are setting a bunch of options in some static way, but not if you're setting them to custom values for each command invocation (because then you'd be dealing with a temp file, which is annoying and error-prone). I'm thinking something like a $GIT_CONFIG_ENV_FILE that is parsed after repo config but before $GIT_CONFIG_PARAMETERS. Or alternatively, add an includeIf directive that lets you do something like: [includeIf "env:FOO"] path = foo.gitconfig which triggers if $FOO is set. But again, that's only useful if you have certain "profiles" of config you're trying to set, and not custom values. -Peff
