f00f

Is mixing stages and accounts a valid model? I'd say the new employee should deploy stage dev (or which ever they use) to their personal aws profile (defined in config...

I observed the same behavior until the "waits and does nothing" yesterday. I killed it with Ctrl+C then, so I cannot comment on the "deploys although 'n' had been entered"...

+1 (tried `!Sub` in `provider.iam.deploymentRole`) Is this limitation stated somewhere in the docs? I would try creating a patch if someone could point me into the right direction to get...

I dug through the code to find `https://github.com/serverless/serverless/blob/main/lib/plugins/aws/provider.js`. There, `provider.iam.deploymentRole` is defined as `awsArn` which in turn allows `awsArnString` and `awsCfFunction`. Looks correct, all the way through till `awsCfSub`. 🤷‍♂️...

Never mind. I found https://github.com/serverless/serverless/issues/8395#issuecomment-708297490 which explains why those CF functions are not supported for `deploymentRole`. I also found that https://github.com/serverless/serverless/pull/9662 introduced `${aws:accountId}` which is exactly what I needed.

Are there plans to implement AES support for `ZipInputStream`? Is there an issue or a PR for it? What's the problem with it?

Also under active-ish development: https://github.com/jessielesbian/ikvm

lgtm

lgtm

I work on Win 10 and run serverless from PowerShell. Don't know the node version I'm using (other pc), but should be 16 or 14. The released package works with...