Open sgreenstein opened 6 years ago
Thanks for the report @sgreenstein! This looks like a pretty straightforward fix. I'll change our options for remote execution / caching to not use null
to indicate the default, but instead an empty string.
FYI @buchgr
will fix.
Hi there, I am also impacted by the same issue. @philwo / @buchgr, do you know if this is still planned to be fixed? @sgreenstein, did you find a workaround to this? Thanks!
Description of the problem / feature request:
If a flag that defaults to null is passed in .bazelrc or bazel.rc, it is impossible to set it to null on the command line.
Feature requests: what underlying problem are you trying to solve with this feature?
Enable remote caching by default, but be able to disable it on the command line. To do this I specify the remote caching flags in bazel.rc, but wish to override them on the command line, which isn't possible.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
bazel.rc:
It is now impossible to set
--google_credentials
tonull
so that it doesn't look for a key:What operating system are you running Bazel on?
Rodete
What's the output of
bazel info release
?0.10.0
Have you found anything relevant by searching the web?
https://stackoverflow.com/questions/48652798/how-do-i-unset-flags-set-in-bazelrc/