Skip to content
New issue

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

feat: env file improvements #3376

Merged
merged 2 commits into from
Oct 18, 2024
Merged

feat: env file improvements #3376

merged 2 commits into from
Oct 18, 2024

Conversation

hassy
Copy link
Member

@hassy hassy commented Oct 18, 2024

Description

  • Make values from a file specified with --dotenv available to workers on Azure
  • Introduce --env-file as an alias for --dotenv

Pre-merge checklist

This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.

  • Does this require an update to the docs? Yes
  • Does this require a changelog entry? Yes

Currently the values set in an env file are only made available
to the Artillery process running in a worker Azure, instead of
being set at the container level.

This means that for example it's impossible to set the DEBUG
environment variable in the worker to help debug issues.

This change makes tests on Azure ACI work in the same way as
tests on AWS Fargate.
Add --env-file as an alias for the existing --dotenv flag.

"--dotenv" is a confusing name when saying it out loud (e.g. on
a support call). "--env-file" is more precise and is also used
by Node.js v20 and above:

https://nodejs.org/dist/latest-v20.x/docs/api/cli.html#--env-fileconfig
@hassy hassy changed the title Fix/dotenv feat: env file improvements Oct 18, 2024
@hassy hassy merged commit 2f24c13 into main Oct 18, 2024
41 checks passed
@hassy hassy deleted the fix/dotenv branch October 18, 2024 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant