.env file support

Environment .env file would be awesome. I know there is environments configuration section and also possibility to override config from command line BUT:

I have more scenarios, which means more .yml files in one folder. And this folder is versioned in Git, so I don’t want to have credentials in .yml files. And credentials are 8 fields with UUID value so it’s not possible to put them in the command line and change them before each test.

So it would be great to have one .env file common for all scripts in the folder. Now I have to create each .yml file twice, one as .yml (Git ignored) and second as .yml.dist where I have to replace credentials with dummy string and put it into the Git.

[vojtasvoboda]

I’m not sure if it helps somehow. My call will be still like that: artillery run -v portal_id=a9605172-a780-4655-af74-bd3fe68b8653,app_id=5973e47c-9d7e-4227-b157-fc1f98a4710e,app_secret=386b6583-744b-4020-9e02-5b309339147a,user_id=d8e18caa-bab7-4e0e-9b1f-639234c8daff,user_secret=d241a7fc-b117-4d4e-8427-809f10d28af7 scenario_01.yml 2> errors_01.txt 1> output_01.txt &

I still believe there is a place for the .env file in the future 😃

[raphaelsaunier]

If it helps anyone, I solved this with dotenv-cli, a small wrapper around dotenv. Once installed, you just prefix your commands with it and it’ll load the contents of the .env located in the same folder:

$ dotenv artillery run …