Ben Fradet

Yes and the fact that the `auth` endpoint doesn't really perform authentication but only key administration (generation, deletion, and soon retrieval with #60).

see snowplow/snowplow#3634

From my tests, it seems the return code from a step isn't reported back up the EMR chain. cf [StepStateChangeReason](https://docs.aws.amazon.com/sdk-for-go/api/service/emr/#StepStateChangeReason)'s Code which is always None.

I haven't dug into the message, it might be capturing stderr, I'll have to try that out. What we do in eer is inspect which step resulted in a failure...

That combined with a way to provide feedback (maybe through StepStateChangeReason's Message) would solve our issue, indeed.

Unfortunately, emr doesn't pick up anything from a script step. ```json { "Step":{ "ActionOnFailure":"CANCEL_AND_WAIT", "Config":{ "Args":[ "s3://snowplow-hosted-assets-eu-central-1/common/emr/snowplow-check-dir-empty.sh", "s3://ben-test-output/processing/raw/" ], "Jar":"s3://eu-central-1.elasticmapreduce/libs/script-runner/script-runner.jar", "MainClass":null, "Properties":{ } }, "Id":"s-14DXZAQ9JXDYD", "Name":"Checking that s3://ben-test-output/processing/raw/ is empty",...

pushing back

@chuwy how should we proceed here? background is in #842

ok thanks, leaving in the 101 milestone for now. @misterpig if you could do the necessary changes, i.e. move to 2-0-0, we could integrate it into release 113.

I think I remember seeing a custom sbt task in another project that would just do this and that would let us do something like: ``` project_version=$(sbt myPrintVersion) ```