[x] I am running the latest version. (up upgrade) v1.3.0
[x] I searched to see if the issue already exists.
[x] I inspected the verbose debug output with the -v, --verbose flag.
[ ] Are you an Up Pro subscriber?
Description
First ever deploy ends in panic and all hell breaks loose. In short I used the AWS execution role name (foobar) instead of its ARN (arn:aws:iam::990099999999:role/foobar).
Error message panic: runtime error: index out of range was not helpful, had to fish out source code and realize that it expects semicolon in role, which lead me to the usage of actual ARN.
Prerequisites
up upgrade
)v1.3.0
-v, --verbose
flag.Description
First ever deploy ends in panic and all hell breaks loose. In short I used the AWS execution role name (
foobar
) instead of its ARN (arn:aws:iam::990099999999:role/foobar
).Error message
panic: runtime error: index out of range
was not helpful, had to fish out source code and realize that it expects semicolon in role, which lead me to the usage of actual ARN.Failing line in your codebase: https://github.com/apex/up/blob/master/platform/lambda/lambda.go#L945
Steps to Reproduce
app.js
up.json
Then run
$ up -v
Stacktrace