We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange but true - in my setup, I have:
name: aws runtime: python3.6 stage: ${opt:stage, self:custom.defaultStage} region: ${self:custom.profiles.${self:provider.stage}.region} profile: ${self:custom.profiles.${self:provider.stage}.profileName} memorySize: 128 timeout: 15 deploymentBucket: name: ${self:provider.stage}-lambda-deployment
And if I use this and do sls package I get:
sls package
Serverless: Load command run Serverless: Load command config Serverless: Load command config:credentials Serverless: Load command create Serverless: Load command install Serverless: Load command package Serverless: Load command deploy Serverless: Load command deploy:function Serverless: Load command deploy:list Serverless: Load command deploy:list:functions Serverless: Load command invoke Serverless: Load command invoke:local Serverless: Load command info Serverless: Load command logs Serverless: Load command login Serverless: Load command logout Serverless: Load command metrics Serverless: Load command remove Serverless: Load command rollback Serverless: Load command rollback:function Serverless: Load command slstats Serverless: Load command plugin Serverless: Load command plugin Serverless: Load command plugin:install Serverless: Load command plugin Serverless: Load command plugin:uninstall Serverless: Load command plugin Serverless: Load command plugin:list Serverless: Load command plugin Serverless: Load command plugin:search Serverless: Load command emit Serverless: Load command config Serverless: Load command config:credentials Serverless: Load command rollback Serverless: Load command rollback:function Serverless: Load command requirements Serverless: Load command requirements:clean Serverless: Load command requirements:install Serverless: Invoke package Serverless: Invoke aws:common:validate Serverless: Invoke aws:common:cleanupTempDir Serverless: Generating requirements.txt from Pipfile... Error -------------------------------------------------- ENOENT: no such file or directory, open '/home/data/home/wattd/dev/wattd/startover/.serverless/requirements.txt'
If I comment out the deploymentBucket lines, it proceeds without errors:
Serverless: Load command plugin Serverless: Load command plugin:search Serverless: Load command emit Serverless: Load command config Serverless: Load command config:credentials Serverless: Load command rollback Serverless: Load command rollback:function Serverless: Load command requirements Serverless: Load command requirements:clean Serverless: Load command requirements:install Serverless: Invoke package Serverless: Invoke aws:common:validate Serverless: Invoke aws:common:cleanupTempDir Serverless: Generating requirements.txt from Pipfile... Serverless: Installing required Python packages with python3.6... etc.
The text was updated successfully, but these errors were encountered:
7a298db
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Strange but true - in my setup, I have:
And if I use this and do
sls package
I get:If I comment out the deploymentBucket lines, it proceeds without errors:
The text was updated successfully, but these errors were encountered: