Intro

You can use an GCS destination to export query results to a Google Cloud Platform GCS bucket.

Once a destination is created, you need only provide run time variables to push an activation file to a remote resource. Saved destinations are available to all users in your company and can be reused indefinitely. 

Pre-requisites

Before starting, you will need the following to hand:

• A  Workload Identity federation credentials JSON file
• Bucket details

You will need to do the following:

• Obtain a credentials JSON file: From the Google Management Interface, generate the key file for the service account. This is a JSON file for a service user that allows InfoSum Bunker to access your Google Cloud Storage bucket. You do not need to amend this file in any way Configuring-Google-Cloud-Platform-Workload-Identity-Federation-Setup
• Set access permissions in GCS: The service user needs to have Create and Write access to the Google Cloud Storage bucket they intend to push files to. If files are pushed to a subfolder, they may need to give explicit permission to Create and Write files to that subfolder.

Creating a GCS destination 

First, select the Destinations tab under Activate and then click New Destination. 

The form below appears when you select GCS as your destination type and the following fields need to be completed:

1. Destination Type: Select GCS.
2. Name: Identifies the destination
3. Description: A free-text explanation of the destination

Once completed, press Next.

Adding GCS connection details

Use destinations to create a connection between the InfoSum Platform and your GCS bucket.

The above form contains the following fields:

1. Bucket: Specify the bucket name (no leading Google Cloud Storage identifier, e.g. "bucket-name" not "GCS://bucket-name")
2. Destination path: path within the bucket.
3. GCS credentials JSON: Copy and paste the credentials JSON file text into here.  

Click Submit. The saved destination is stored on the Platform’s Destinations page and can be selected in the Activations tab when pushing an activation file to a remote resource. The destination can be reused and is available to all users in your company