Deployment never ends if explicitly specified lambda role doesn't exist
Open
bug
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 383
- PR merge metrics
- No merged PRs in 30d
Description
Deployment never ends if there is a lambda role specified in `up.json` and that role doesn't exist. There is no indication what it's doing unless verbose mode is enabled. Verbose mode produces never ending stream of `DEBU waiting for role to be created` messages. It should fail immediately in such cases.
Contributor guide
Assessment
This issue has not been assessed yet.