"Error: No target specified and no environment chosen" in AWS Fargate container

[manuelcarriernunesatsap]

When artillery-script-02.yml is run via

$Env:TARGET_URL = 'http://asciiart.artillery.io:8080'
artillery run-fargate 'artillery-script-02.yml' --region='eu-central-1' --count=1 --output='report.json'

Error: No target specified and no environment chosen is output to the logs generated by the AWS Fargate container. The run-fargate-error-02 branch in the manuelcarriernunesatsap/artillery repo contains files and instructions to facilitate reproducing this.

Version info

Artillery: 2.0.10
Node.js: v20.12.2
OS: win32

[bernardobridge]

Hey @manuelcarriernunesatsap 👋 !

Environment variables need to be propagated to Fargate containers using a dotenv file with the --dotenv flag. That's why it's erroring, since it would just resolve to undefined.

[manuelcarriernunesatsap]

Thanks for the quick 💨 response, @bernardobridge 😃

Is that something that changed along the way? 💭

[bernardobridge]

Hi @manuelcarriernunesatsap ! I don't think so, no 🤔, not for Fargate. Did you have a different experience at one point?

[manuelcarriernunesatsap]

My possible experience would have occurred many months ago, which I can't remember. I asked to see if it was even possible that I have experienced such a thing.

Thanks, @bernardobridge .

[bernardobridge]

Oh okay! Glad it's working now! 👍