Welcome Guest! Log in


This article describes the principal changes of Google Cloud Platform Component.

The connector download section can be found at this page.

Note:

Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

This article is dedicated to Stambia DI 2020 (S20)

If you are using Stambia DI S17, S18 and S19 please refer to this article.

component.google.platform.2.0.3

Prerequisistes

  • Stambia DI Designer 2020 (S20.1.0) or higher

When you are working with Google Cloud Storage Metadata, you need to define the Google Cloud Platform Credentials to be able to perform operations on the storage.

A new wizard has been added to propose selecting the corresponding credentials, which will be displayed when creating a new storage Metadata or when launching the wizard from an existing Metadata.

This wizard has been added to ease the configuration and usability of Google Storage Metadata.

Note that the credentials proposed in this wizard are retrieved from all Google Cloud Platform Metadata of current workspace, in which credentials are defined.

All existing credentials are displayed automatically.

Just select one and click on Finish select the credentials.

storage.wizard

component.google.platform.2.0.2

TOOL GCS Put Blobs

Performance improvements when sending large files into Google Storage.

component.google.platform.2.0.1

Credentials revision

A new attribute "Credentials File Format" has been added to choose how the credentials will be provided.

Note that for backward compatibility, the previously used "Json Key String" attribute, which has been moved to "deprecated" tab, has priority on the new format attribute.

To use the new mechanism, you must remove the value in the old attribute and then define the link.

The new format attribute is proving the two following formats:

Action Description
Localfile Absolute file path to the JSON private key file corresponding to the account to connect with. Note that it must be accessible by the Runtime on the file system.
String JSon Access token string. This corresponds to the unencrypted content of the JSON private key file corresponding to the account to connect with.

Example of local file

gcp01b

Example of string

gcp02

The advantage of string format is that, instead of using a file path as with the other attribute, you specify the credentials directly in Metadata, so you do not have to store a local file somewhere that can be accessed by the Runtime.

The downside is that this attribute is stored as plain text inside the Metadata.

We advise to use it for development purposes, and to consider using the local file option instead for production environments.

You have no rights to post comments

Articles

Suggest a new Article!