Google Cloud Storage with YAML

YAML parameters for Google Cloud Storage

You can find the list with common parameters for all Buddy actions here.

NameTypeDescription
action
Required		StringThe ID of the action.
type
Required		StringThe type of the action. Should be set to GCS.
bucket_name
Required		StringThe name of the GCS Bucket.
integration_id
Required		IntegerThe ID of the integration.
input_typeStringDefines whether the files are deployed from the repository or from the build filesystem. Can be one of SCM_REPOSITORY or BUILD_ARTIFACTS.
local_pathStringThe path in the repository.
public_accessBooleanMakes files accessible through public HTTP.
remote_pathStringThe absolute or relative path on the remote server.
run_only_on_first_failureBooleanDefines whether the action should be executed on each failure. Restricted to and required if the trigger_time is ON_FAILURE.
deployment_excludesString[]The paths and/or files that will be left out during the deployment.
deployment_includesString[]The exceptions from the ignore patterns set in deployment_excludes.
application_nameStringThe name of the GCS application.
disabledBooleanWhen set to true the action is disabled. By default it is set to false.

YAML example for Google Cloud Storage

actions:
  - action: "Upload files to GCS/buddy"
    type: "GCS"
    input_type: "SCM_REPOSITORY"
    local_path: "/assets"
    remote_path: "/public"
    bucket_name: "buddy"
    public_access: true
    application_name: "buddy-tests-112923"
    integration_id: 1
    deployment_excludes:
    - "/tmp"
    - "*.log"
    deployment_includes:
    - "/tmp/assets"
    - "/tmp/styles"
Questions?

Not sure how to configure a pipeline for your process? Reach out on the live-chat, contact support, or ask our community on our forum.

Sign up for Buddy Digest

Best practices on CI/CD and fresh changelogs delivered weekly to your inbox.