Installation steps

Gluesync SQL to NoSQL for Google Cloud Storage

Prerequisites

To have Gluesync working on your Google Cloud Storage instance you will need to have:

  • a Google Cloud Storage bucket;

  • a configured Service account with:

    • permission as Storage Object Admin, Storage Object Creator, Storage Object Viewer;

    • a key (in JSON format) associated with this account created via your GCP console;

Basic configuration example

This module can be customized by using a configuration file, in JSON format. The file name to use must be specified as a parameter when launching the app, with the -f or --file tokens. The file should be composed of a union of the common configuration file (see here Installation steps) and source-specific configuration:

{
  ...
  // (source section omitted)
  ...
  "targetName": "myBucketName",
  ...

  "gcpStorage": {
    "credentialsPath": "/path/to/file/service-account-name-abXXXXXe3f.json",
    "allowObjectsDeletion": false
  },
}

The parameters that refer to a target are the parameters that describe the connection to the Google Cloud Storage bucket.

  • targetName: the name of the target bucket as represented inside your Google Cloud Storage console;

Other configuration parameters are the following:

Google Cloud Storage-specific configurations are listed under the gcpStorage property:

  • credentialsPath: the path that points to your .json key file downloaded right from Google Cloud console after having created your Service account;

  • timeoutSeconds (optional): defaults to 60. Number of seconds to set as timeout for operations involving communication with the destination;

  • allowObjectsDeletion (optional): defaults to true. If set to false tells Gluesync to skip any action that involves data deletion committed into the source database: Gluesync will propagate only events that involve Insert(s) and Update(s).