5 ms·

You can't run AWS lambda or DyanmoDB locally too (well you can but it's a hassle). So by that logic, we shouldn't use them at all. I don't like working with CI

You can't run AWS lambda or DyanmoDB locally too (well you can but it's a hassle). So by that logic, we shouldn't use them at all. I don't like working with CI too but I'll take GitHub Actions over Jenkins/CircleCI/TravisCI any day.

chriswarbo 2y ago
> You can't run AWS lambda or DyanmoDB locally too (well you can but it's a hassle). So by that logic, we shouldn't use them at all. No, applying the logic to something like Lambda would mean implementing handlers like: function handle(lambdaRequest, lambdaContext) { return myFunction( stuffExtractedFromLambdaRequest(lambdaRequest), stuffExtractedFromLambdaContext(lambdaContext) ); } Then there's no need to go through the hassle of running Lambda functions locally; since we can just run `myFunction` locally instead. Dynamo isn't the same, since it's just a service/API that we call; we don't implement its logic, like we do for CI tasks, Lambda functions, etc. Whilst you're right that it's a hassle to run DynamoDB locally (although not too bad, in my experience); that's also not necessary. It's fine to run code locally which talks to a remote DynamoDB; just set up the credentials appropriately.
- rednafi 2y ago
  Yeah, and that doesn't stop us from using either of them. What I tried to convey is that GHA isn't ideal and it has a few warts but it's still better than most of the options available out there.
sunshowers 2y ago
The problem with the analogy is that GHA's interface is quite thick.
arccy 2y ago
lambda: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli-local.html https://docs.aws.amazon.com/serverless-application-model/lat... dynamodb: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.DownloadingAndRunning.html#docker https://docs.aws.amazon.com/amazondynamodb/latest/developerg... doesn't seem any harder than running any other db

chriswarbo 2y ago

> You can't run AWS lambda or DyanmoDB locally too (well you can but it's a hassle). So by that logic, we shouldn't use them at all. No, applying the logic to something like Lambda would mean implementing handlers like: function handle(lambdaRequest, lambdaContext) { return myFunction( stuffExtractedFromLambdaRequest(lambdaRequest), stuffExtractedFromLambdaContext(lambdaContext) ); } Then there's no need to go through the hassle of running Lambda functions locally; since we can just run `myFunction` locally instead. Dynamo isn't the same, since it's just a service/API that we call; we don't implement its logic, like we do for CI tasks, Lambda functions, etc. Whilst you're right that it's a hassle to run DynamoDB locally (although not too bad, in my experience); that's also not necessary. It's fine to run code locally which talks to a remote DynamoDB; just set up the credentials appropriately.

rednafi 2y ago
Yeah, and that doesn't stop us from using either of them. What I tried to convey is that GHA isn't ideal and it has a few warts but it's still better than most of the options available out there.

sunshowers 2y ago

The problem with the analogy is that GHA's interface is quite thick.

arccy 2y ago

lambda: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli-local.html https://docs.aws.amazon.com/serverless-application-model/lat... dynamodb: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.DownloadingAndRunning.html#docker https://docs.aws.amazon.com/amazondynamodb/latest/developerg... doesn't seem any harder than running any other db