Cloudfront with YAML

Tip

Learn more about: - CloudFront action features - CloudFront integrations - CloudFront alternatives

YAML parameters for Cloudfront

Hint

List with common parameters for all Buddy actions

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 `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

yaml
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: "my_integration"
  timeout: 900
  deployment_excludes:
  - "/tmp"
  - "*.log"
  deployment_includes:
  - "/tmp/assets"
  - "/tmp/styles"

Last modified on Mar 4, 2025

Cloudflare Code sign and export an iOS app

On this page

YAML parameters for Cloudfront YAML example for Cloudfront