Feature request: read settings from environment variables as well as command line #2395
Comments
alexcrichton
added a commit
to alexcrichton/cargo
that referenced
this issue
Feb 19, 2016
This commit adds a more principled system to rationalize what ends up being a configuration value versus an environment variable. This problem is solved by just saying that they're one and the same! Similar to Bundler, this commit supports overriding the `foo.bar` configuration value with the `CARGO_FOO_BAR` environment variable. Currently this is used as part of the `get_string` and `get_i64` methods on `Config`. This means, for example, that the following environment variables can now be used to configure Cargo: * CARGO_BUILD_JOBS * CARGO_HTTP_TIMEOUT * CARGO_HTTP_PROXY Currently it's not supported to encode a list in an environment variable, so for example `CARGO_PATHS` would not be read when reading the global `paths` configuration value. cc rust-lang#2362 cc rust-lang#2395 -- intended to close this in tandem with rust-lang#2397
bors
added a commit
that referenced
this issue
Feb 26, 2016
This commit adds a more principled system to rationalize what ends up being a configuration value versus an environment variable. This problem is solved by just saying that they're one and the same! Similar to Bundler, this commit supports overriding the `foo.bar` configuration value with the `CARGO_FOO_BAR` environment variable. Currently this is used as part of the `get_string` and `get_i64` methods on `Config`. This means, for example, that the following environment variables can now be used to configure Cargo: * CARGO_BUILD_JOBS * CARGO_HTTP_TIMEOUT * CARGO_HTTP_PROXY Currently it's not supported to encode a list in an environment variable, so for example `CARGO_PATHS` would not be read when reading the global `paths` configuration value. cc #2362 cc #2395 -- intended to close this in tandem with #2397
|
Ah this was implemented in #2398, yay! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the Rust build system, all actual calls to Cargo are buried within several layers of scripts, but it's easy to set environment variables. If others try to automate the builds of Rust projects that use Cargo, they may encounter similar challenges.
In the case that caused me to file this issue, it would be convenient for Cargo to read a var like
CARGO_VERBOSEinstead of only the command-line--verbosewhen deciding how much debug info to print.The text was updated successfully, but these errors were encountered: