Helix Content Bus

Serverless action that pushes helix-content-proxy into a storage service

Note: The content-bus action is no longer used. its functionality is now embedded in helix-admin.

Status

Installation

Usage

The following parameters should be passed when invoking the action:

• owner: GitHub repository owner
• repo: GitHub repository name
• ref: GitHub repository reference or branch
• path: path to the document to be fetched from helix-content-proxy
• prefix: prefix to add to the S3 address, defaults to live

Note: the first three parameters also determine the location where the fstab.yaml configuration file is downloaded from. The service requires that file to find a matching mount point, which also determines the bucket name used in S3.

The following environment variables are optional:

• AWS_S3_REGION: AWS region
• AWS_S3_ACCESS_KEY_ID: AWS access key associated with an IAM user or role
• AWS_S3_SECRET_ACCESS_KEY: Specifies the secret key associated with the access key

If they're not specified, the function operates with whatever role it was deployed with.

Development

Deploying Helix Content Bus

All commits to main that pass the testing will be deployed automatically. All commits to branches that will pass the testing will get commited as /helix-services/content-bus@ci<num> and tagged with the CI build number.