Hoss Man
Hoss Man
Here's what i think is happening: * `Config.getAuthenticatorCommandFromExecConfig()` is straight up ignoring `exec.getCommand()` unless `exec.getArgs()` is non-null. * `ExecConfig.args` defaults to `new ArrayList();` ... which gets used when the `ExecConfig`...
I'm attaching the simplest possible test patch i can think of that demonstrates (on non-windows OS) the various problems with how the "stringification" of the command + arguments is handled...
This bug still exists, and is trivial to reproduce.
I haven't tried out either PR, because frankly I didn't feel like it was worth my time to help test out any solution that continues to use `String.join(...)` on arguments...
The specific circumstances as described -- *USING GCP/GKE* -- is still a "problem", but AFAICT from digging into the code and some previuosly closed issues, this problem is not due...
Assuming everything i said is correct, and I'm not missunderstanding something, then short answer: "Yes" ... using the `auth-helper.sh` I posted -- instead of using `gcloud container clusters get-credentials ...`...
> So it would be nice if there were some way to say ... "any more than n violations of this rule across the whole project causes a failure, but...
> ... not sure if it should be the same metadata key though ? Given the current design of `sigal` -- where an album can either have sub-albums or images,...
rather then taking in another selector string for the `container` (and adding special code in the toc function to look for `closest(container)`) it seems like it would be more flexible...
Hmmm... ok, so bfacbc24d5443899a6c7daaab801b79996b400fd is totally unrelated ... apparently i merged that into my coercedates branch w/o realizing it. sorry for the noise.