
Research
/Security News
Critical Vulnerability in NestJS Devtools: Localhost RCE via Sandbox Escape
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
This is a pytest
plugin that enables you to set environment variables in a pytest.ini
or pyproject.toml
file.
Install with pip:
pip install pytest-env
pyproject.toml
[tool.pytest_env]
HOME = "~/tmp"
RUN_ENV = 1
TRANSFORMED = {value = "{USER}/alpha", transform = true}
SKIP_IF_SET = {value = "on", skip_if_set = true}
The tool.pytest_env
tables keys are the environment variables keys to set. The right hand side of the assignment:
transform
or skip_if_set
keys, while the value
key holds the
value to set (or transform before setting). For transformation the variables you can use is other environment
variable,In your pytest.ini file add a key value pair with env
as the key and the environment variables as a line separated
list of KEY=VALUE
entries. The defined variables will be added to the environment before any tests are run:
[pytest]
env =
HOME=~/tmp
RUN_ENV=test
Or with pyproject.toml
:
[tool.pytest.ini_options]
env = [
"HOME=~/tmp",
"RUN_ENV=test",
]
You can use D:
(default) as prefix if you don't want to override existing environment variables:
[pytest]
env =
D:HOME=~/tmp
D:RUN_ENV=test
You can use existing environment variables using a python-like format, these environment variables will be expended before setting the environment variable:
[pytest]
env =
RUN_PATH=/run/path/{USER}
You can apply the R:
prefix to keep the raw value and skip this transformation step (can combine with the D:
flag,
order is not important):
[pytest]
env =
R:RUN_PATH=/run/path/{USER}
R:D:RUN_PATH_IF_NOT_SET=/run/path/{USER}
FAQs
pytest plugin that allows you to add environment variables.
We found that pytest-env demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
Product
Customize license detection with Socket’s new license overlays: gain control, reduce noise, and handle edge cases with precision.
Product
Socket now supports Rust and Cargo, offering package search for all users and experimental SBOM generation for enterprise projects.