Continuous processes in cmd do not trigger subsequent builds

[andrehoong-pixieset]

Hello, I am trying to set up air for an AWS Lambda development environment. I have this cmd defined in the .air.toml file:
cmd = "go build -o ./tmp/main . ; ~/.aws-lambda-rie/aws-lambda-rie ./go/main main.handle

The idea is whenever air rebuilds the executable we launch aws-lambda-rie with that new executable. My issue is when using this command, air does not rebuild any changes. In the logs I will only get main.go has changed , but no build is triggered after that.

I suspect this is because ~/.aws-lambda-rie/aws-lambda-rie ./go/main main.handle starts an ongoing process and as a result running cmd does not return an exit code. I was considering running the aws-lambda-rie through the post_cmd, but it looks like that isn't implemented at all.

Any suggestions are greatly appreciated!