Fix crash when starting specifying a non-existent lambda function

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Atlas Streams
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, we don't handle the error produced from calling a non-existent lambda function gracefully. This isn't caught in our lambda_local js tests. This is most likely due to the lambda container running a successful dry run.

            Assignee:
            Unassigned
            Reporter:
            Guy-Jacques Isombe
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: