Cloudfront with YAML
YAML parameters for Cloudfront
| Name | Type | Description |
|---|---|---|
action Required | String | The name of the action. |
type Required | String | The type of the action. Should be set to CLOUDFLARE. |
distribution_id Required | String | The ID of the Cloudfront web distribution. |
integration_hash Required | String | The ID of the integration. |
| input_type | String | Defines whether the files are deployed from the repository or from the build filesystem. Can be one of SCM_REPOSITORY or BUILD_ARTIFACTS. |
| local_path | String | The path in the repository. |
| base_url | String | The absolute or relative path on the remote server. |
| purge_all | Boolean | Specifies whether or not the whole cache should be removed. |
| deployment_excludes | String[] | The paths and/or files that will be left out during the deployment. Available only if purge_all is set to false. |
| deployment_includes | String[] | The exceptions from the ignore patterns set in deployment_excludes. |
YAML example for Cloudfront
actions:
- action: "Cloudfront action"
type: "CLOUD_FRONT"
input_type: "SCM_REPOSITORY"
local_path: "/"
distribution_name: "buddy.works"
distribution_id: "EDFDVBD632BHDS5"
purge_all: false
base_url: "/merged"
integration_hash: "5ddb7c180fb38be67bd78a88a"
timeout: 900
deployment_excludes:
- "/tmp"
- "*.log"
deployment_includes:
- "/tmp/assets"
- "/tmp/styles"Last modified on February 16, 2023