This article describes the principal changes of Google Cloud Platform (GCP).
The connector download section can be found at this page.
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 S17, S18 and S19 addon .
If you are using Stambia DI 2020 (S20) or higher, please refer to this article.
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:
|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
Example of string
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.