Skip to content

Latest commit

 

History

History
34 lines (29 loc) · 1.9 KB

update.md

File metadata and controls

34 lines (29 loc) · 1.9 KB

#update

Deploy a new version of the Lambda function using project files, update any associated web APIs

Usage

claudia update {OPTIONS}

Options

  • --version: (optional) A version alias to automatically assign to the new deployment
  • For example: development
  • --source: (optional) Directory with project files
  • Defaults to: current directory
  • --config: (optional) Config file containing the resource names
  • Defaults to: claudia.json
  • --no-optional-dependencies: (optional) Do not upload optional dependencies to Lambda.
  • --use-local-dependencies: (optional) Do not install dependencies, use local node_modules directory instead
  • --cache-api-config: (optional) Name of the stage variable for storing the current API configuration signature. If set, it will also be used to check if the previously deployed configuration can be re-used and speed up deployment
  • For example: claudiaConfigCache
  • --keep: (optional) keep the produced package archive on disk for troubleshooting purposes. If not set, the temporary files will be removed after the Lambda function is successfully created
  • --use-s3-bucket: (optional) The name of a S3 bucket that Claudia will use to upload the function code before installing in Lambda. You can use this to upload large functions over slower connections more reliably, and to leave a binary artifact after uploads for auditing purposes. If not set, the archive will be uploaded directly to Lambda
  • For example: claudia-uploads
  • --set-env: (optional) comma-separated list of VAR=VALUE environment variables to set
  • For example: S3BUCKET=testbucket,SNSQUEUE=testqueue
  • --set-env-from-json: (optional) file path to a JSON file containing environment variables to set
  • For example: production-env.json
  • --env-kms-key-arn: (optional) KMS Key ARN to encrypt/decrypt environment variables