Google Cloud Storage with YAML

Tip

Learn more about: - Google Cloud Storage action features - Google Cloud Storage integrations - Google Cloud Storage alternatives

YAML parameters for Google Cloud Storage

Hint

List with common parameters for all Buddy actions

Name	Type	Description
action `Required`	String	The ID of the action.
type `Required`	String	The type of the action. Should be set to `GOOGLE_CLOUD_STORAGE`.
bucket_name `Required`	String	The name of the GCS Bucket.
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.
public_access	Boolean	Makes files accessible through public HTTP.
remote_path	String	The absolute or relative path on the remote server.
deployment_excludes	String[]	The paths and/or files that will be left out during the deployment.
deployment_includes	String[]	The exceptions from the ignore patterns set in `deployment_excludes`.
application_name	String	The name of the GCS application.
content_encoding	String	ContentEncoding that will be set for the deployed files e.g. "gzip".

YAML example for Google Cloud Storage

yaml
actions:
- action: "Upload files to GCS/hello-world-0"
  type: "GOOGLE_CLOUD_STORAGE"
  input_type: "SCM_REPOSITORY"
  local_path: "/assets"
  remote_path: "/public"
  bucket_name: "hello-world-0"
  application_name: "hello-world"
  application_display_name: "hello-world"
  integration: "my_integration"
  deployment_excludes:
  - "/tmp"
  - "*.log"
  deployment_includes:
  - "/tmp/assets"
  - "/tmp/styles"

Last modified on Mar 4, 2025

Google Cloud Run Google Compute Engine