Remove default AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars

[lambci]

Remove default AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars

[mhart]

Trying to understand the use case – is it because you've added this check to your Lambda fn and you're trying to get coverage on it, or something similar to this?

If so, then I think the check itself (or at least, trying to get 100% coverage on it) is suspect. It's akin to checking whether the event arg exists, or whether the context arg has a get_remaining_time_in_millis property on it, and checking whether it's a function or not. You certainly could add these checks, but you really shouldn't. If these things aren't set, then there are much bigger problems 😉

If this isn't the case you're trying to add this option for, then I think I still don't fully understand the use case

[mhart]

@simonvanderveldt but they're always set on AWS Lambda

[simonvanderveldt]

@mhart Yeah, but that's not the case when running them locally in Docker :)
This is mainly meant for our CI since we want to automatically validate the Lambda's we write

[mhart]

@simonvanderveldt but then I'm not sure what you mean by "validate the Lambdas we write"?

The variable is always set on AWS Lambda and this docker image / test runner is trying to replicate that environment as closely as possible

[mhart]

Closing this – let me know if I've misunderstood your use case somehow