Ganey

> Current axios version is now 0.23.0 I'm not confident with 0.23.0 yet as i'm not sure if the 'breaking changes' section of the axios [change log](https://github.com/axios/axios/blob/master/CHANGELOG.md) affects the cache...

Thanks @pstenstrm I've updated the semver in the PR to `>=0.21.1

I'm guessing the limits are those described here: https://firebase.google.com/docs/auth/limits#api_limits `Operations per service account | 500 requests/second` Which IMO is a relatively small amount. What happens if you want to edit...

@prameshj This is still a blocker for me (I'm sure it must affect others) Does the firebase team/google have any intention of supporting this in the near future?

@timkelty take a look at https://serverless.com/framework/docs/providers/aws/guide/variables/ You can then import bucket name from a file: `${file(./env-vars.yml):image_bucket, "default-s3-bucket"}` Just swap the env-vars.yml out when deploying to different environments

You can run npm install with `--arch=x64 --platform=linux` to ensure you get the linux binaries for the lambda AMI I previously put in a [PR](https://github.com/venveo/serverless-image-handler/pull/1/files) on the old repo that...

Hmm, that's true, I already have that problem after deploying & then trying tests on a different fork I'm working with. The only downside I can see with the docker...

+1 for this feature

Also an issue on MacOS v6.0.2 It breaks if the first two characters after the % are 0-9 or A-F Is the issue somewhere around here? https://github.com/getinsomnia/insomnia/blob/develop/packages/insomnia-url/src/querystring.js#L242

I'm also interested in this, parsing an access token and calling firestore in a single request can take ages when cold on AWS lambda