nix/tests/functional/impure-env.nix

{ var, value }:

with import "${builtins.getEnv "_NIX_TEST_BUILD_DIR"}/config.nix";

mkDerivation {
  name = "test";
  buildCommand = ''
    echo ${var} = "''$${var}"
    echo -n "''$${var}" > "$out"
  '';

  impureEnvVars = [ var ];

  outputHashAlgo = "sha256";
  outputHash = builtins.hashString "sha256" value;
}
Allow CLI to pass environment variables to FOD builder (#8830) Add a new experimental `impure-env` setting that is a key-value list of environment variables to inject into FOD derivations that specify the corresponding `impureEnvVars`. This allows clients to make use of this feature (without having to change the environment of the daemon itself) and might eventually deprecate the current behaviour (pick whatever is in the environment of the daemon) as it's more principled and might prevent information leakage. 2023-10-11 11:58:42 +00:00			`{ var, value }:`

No longer copy functional tests to the build dir This should make `_NIX_TEST_ACCEPT=1` work again, fixing #11369. Progress on #2503 2024-11-01 13:56:50 +00:00			`with import "${builtins.getEnv "_NIX_TEST_BUILD_DIR"}/config.nix";`
Allow CLI to pass environment variables to FOD builder (#8830) Add a new experimental `impure-env` setting that is a key-value list of environment variables to inject into FOD derivations that specify the corresponding `impureEnvVars`. This allows clients to make use of this feature (without having to change the environment of the daemon itself) and might eventually deprecate the current behaviour (pick whatever is in the environment of the daemon) as it's more principled and might prevent information leakage. 2023-10-11 11:58:42 +00:00
			`mkDerivation {`
			`name = "test";`
			`buildCommand = ''`
			`echo ${var} = "''$${var}"`
			`echo -n "''$${var}" > "$out"`
			`'';`

			`impureEnvVars = [ var ];`

			`outputHashAlgo = "sha256";`
			`outputHash = builtins.hashString "sha256" value;`
			`}`