Error messages are not displayed about gander-cli HOT 2 CLOSED

I've found the issue and some behaviour I don't understand.

Originally, the only error the would be displayed was the error from creating an IAM group and user with a reused name. This error came from Amazon and is of type string.

The other errors that I am able to invoke but were not being displayed include:

• creating VPCs: reaching the maximum number of VPCs allowed
• creating a subnet: giving an incorrect availability zone
• creating EFS: reusing a creation token
  All of these errors are of type object. The Ora spinner expects a string, which is why the spinner couldn't display the error message.

To fix this issue, I have created a utility method stringifyErrorMsg that checks for the type of error. If it receives an object, it retrieves the string at the key stderr and returns it.

Unknown behaviour

The other errors I can invoke are of type object because they are being returned by the catch block in executeProcess.js. However, the error from creating the IAM group and user are being returned by the if statement inside the try block. I don't understand why these errors are being handled differently.

from gander-cli.

I investigated the unknown behaviour more by invoking as many errors as I could in as many AWS API calls as possible, namely by passing in false IDs, and have come to conclude the following about the unknown behaviour.

All errors we receive seem to be returned by the catch block. As soon as the executed bash script fails, the code moves on to the catch block, skipping all code in the try block following the script execution.

However, the error received from reusing an IAM group and user name is not caught by the catch block. Thus, the if statement inside the try block - is the only place that it will get caught. I don't know why this one particular error that I can invoke isn't caught.

I don't understand why this behaviour happens, but it does.

from gander-cli.