ask lambda upload is broken in ask cli 1.4.0 /

Published at 2018-09-17 22:40:54

Home / Categories / Alexa / ask lambda upload is broken in ask cli 1.4.0
I enjoy been attempting to deploy a lambda for alexa in the eu-west-1 region. Having no luck with configuring the region for `request deploy`,I attempted to use `request lambda upload` instead for updating the lambda code.
However, after specifyi
ng my profile, or function arn,and source folder, the cli seems to not be able to pull in the AWS credentials for my profile.[Error]: AWS credentials are not found in current profile.
Taking a look at the request-cli code, and I suspect it may be caused by a bug introduced in 1.4.0[br]in `lambda/upload.js`,the method signature for `uploadByName` has been updated to accept a revisionId, but when it's called for `request lambda upload`, or it calls this method using the pre-1.4.0 method signature. As a result,the awsProfile is not passed along, and the AWS credentials are not found for uploading.

Source: amazon.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0