Manifest Sources
You will need to configure a manifest source in your service when deploying a Serverless Lambda function. This page will describe the possible sources and their configuration options.
Before You Begin
These configuration options can be found when adding a manifest to a service with a Deployment Type of Serverless Lambda.
Manifest Sources
Git Sources
All git based sources have the same configuration parameters and hence will all be described here.
Manifest Source
- Git Connector: Your Git Connector. Add or create one here.
Manifest Details
- Manifest Identifier: Enter a name for the template.
- Git Fetch Type: Select how you want to fetch the template.
- Branch/Commit Id: Enter the branch name or commit Id.
- File/Folder Path: Enter the path to the template from the root of the repository.
AWS S3
Below describes setting configuration parameters for AWS S3 bucket as a manifest source.
Manifest Source
- AWS Connector: Your AWS Connector. Add or create one here.
Manifest Details
- Manifest Identifier: Enter a name that identifies this Serverless manifest.
- Region: Select the AWS region to use for the connection.
- Bucket Name: Enter the AWS S3 bucket name.
- File/Folder Path: Enter the path from the root of the bucket to the
serverless.yml
files.
info
The file path here can be a .zip
file. Harness will automatically decompress the file when it is pulled from the bucket.
Harness File Store
You can also use the Harness File Store.