AWS deployment fails about invokust

[csillab]

Can you please share the following:

• which version of invokust you're using?
• the code where you called create_settings

Thanks.

[asantoz]

Hi @csillab ,

I'm using the latest version on pip (0.73) and I'm using the same files locustfile_example.py and lambda_locust.py that are on the repository.
The create_settingsinvocation is here

When in search in python-packages folder seems pip is pulling to me locust dependency version 0.13.5 it's correct?

Thanks 🙏

[csillab]

I'll try to reproduce it tomorrow. I am unsure at the moment where the num_requests param is coming from. :)

There has been some changes in the code and in the example between invokust version 0.73 and 1.0 which is the current master now. Are you using the example in the master or from the 0.73 tagged version?

[asantoz]

Nice @csillab :) I'm using master version.

[csillab]

Can you try select the right tag (0.73) and see if that example works for you? If that does not work, still happy to take a look tomorrow.

[asantoz]

With tag 0.73 example works well 🎉

Some things I have to diverge from the documentation examples, let's take a look 😃

Invoke command

The only thing that doesn't work, is this command 👇

aws lambda invoke --function-name lambda_locust --invocation-type RequestResponse --payload '{"locustfile": "locustfile_example.py", "host":"https://example.com", "num_requests":"20", "num_clients": "1", "hatch_rate": "1", "run_time":"3m"}' output.txt

Which gave me this error 💥

Invalid base64: "{"locustfile": "locustfile_example.py", "host":"https://example.com", "num_requests":"20", "num_clients": "1", "hatch_rate": "1", "run_time":"3m
"}"

I used this argument to workaround that --cli-binary-format raw-in-base64-out.

Invoke Payload

It seems the payload has some incompatibilities on number_request field returning the error

Locust exception TypeError("create_settings() got an unexpected keyword argument 'num_requests'",)

but remove them it works like a charm 😄

Make sense to create a PR to edit these "possible" issues on documentation?
About version 1.0a is already advisable to use?

Thanks a lot for your attention @csillab

[csillab]

Nice, thanks for the detailed info :) I am glad you could make it work.

I'd love for someone to test 1.0a0 "live". That's compatible with the new major release of locust. Please report any issues with it and happy to take a look in my free time :)

That num_requests is definitely wrong there. A PR is welcome to fix it up for master, seems to be wrong there too. :)

[FutureSharks]

I will close this now 🙂