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
I would like to specify the base url. at which to download bazel in a manner that is able to be managed by source control.
My use case is that I want to ensure that users of my project are directed to a site that would be available to them without needing to configure proxies in a corporate environment. (Related to #115)
It would seem like creating a .bazeliskrc or something could be useful for setting these the controls that are currently only configurable via env vars. I would not be opposed to leveraging a key-value system inside the .bazelversion but I'm not sure of the number of tools that leverage this file and that would be appropriate.
I imagine this file could also be used for the following in the future:
Setting SHAs per-platform to verify the downloads (in the case of non-floating versions)
Multiple fallback urls (similar to http_archive)
Persisting "The Company's" BAZELISK_GITHUB_TOKEN as to not require each dev to set it to avoid tripping rate limits
Override the default cache directory
What do you think of this approach?
The text was updated successfully, but these errors were encountered:
Replace `os.Getenv` with `getEnvOrConfig`, which falls back to parsing
key=value pairs from a `.bazeliskrc` file in the workspace
root. Environment variables take precedence.
Aims to solve #119 as simply as possible.
Closes#127.
I would like to specify the base url. at which to download bazel in a manner that is able to be managed by source control.
My use case is that I want to ensure that users of my project are directed to a site that would be available to them without needing to configure proxies in a corporate environment. (Related to #115)
It would seem like creating a
.bazeliskrcor something could be useful for setting these the controls that are currently only configurable via env vars. I would not be opposed to leveraging a key-value system inside the.bazelversionbut I'm not sure of the number of tools that leverage this file and that would be appropriate.I imagine this file could also be used for the following in the future:
http_archive)BAZELISK_GITHUB_TOKENas to not require each dev to set it to avoid tripping rate limitsWhat do you think of this approach?
The text was updated successfully, but these errors were encountered: