We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOME_ENV_VAR
WHITELIST_ENVS="SOME_ENV_VAR"
$ cat logs | grep sensitive\ value | jq .message "listening for jobs, WORKER_GROUP: default, config: WorkerConfig { worker_tags: [\"ansible\", \"bash\", \"bun\", \"csharp\", \"deno\", \"dependency\", \"flow\", \"go\", \"hub\", \"other\", \"php\", \"powershell\", \"python3\", \"rust\"], priority_tags_sorted: [PriorityTags { priority: 0, tags: [\"ansible\", \"bash\", \"bun\", \"csharp\", \"deno\", \"dependency\", \"flow\", \"go\", \"hub\", \"other\", \"php\", \"powershell\", \"python3\", \"rust\"] }], dedicated_worker: None, init_bash: None, cache_clear: None, additional_python_paths: None, pip_local_dependencies: None, env_vars: {\"SOME_ENV_VAR\": \"some sensitive value\"} }"
It would be ideal to be able to toggle this so that it does not dump env_vars.
env_vars
The text was updated successfully, but these errors were encountered:
rubenfiszel
No branches or pull requests
SOME_ENV_VAR
with a sensitive value on a worker, and allowed it withWHITELIST_ENVS="SOME_ENV_VAR"
It would be ideal to be able to toggle this so that it does not dump
env_vars
.The text was updated successfully, but these errors were encountered: