Getting Started with Google Cloud Platform


This getting started gives some clues to start working with Google Cloud Platform

It explains how to create the Google Cloud Project Metadata that will contain account and credentials information.

This Metadata will then be used in all related Google Cloud technologies.

This Metadata is the main entry point for account and credentials definition, and is a prerequisite to use any other related Google Cloud Metadata.

Metadata Configuration


The first step is to create a Google Cloud Project Metadata.

Launch the Metadata creation wizard, select the Google Cloud Project Metadata in the list and follow the wizard.


The first information to define in Metadata is the Google Cloud Project Identifier, which is the unique identifier of the project you want to work on.

Check with your administrator or lead to Google Cloud Project’s console page in your browser to find it, and then define it in Metadata.

getting started google cloud platform project id

Next step is to define credentials to connect and perform operations on the project.

For this, create an Account node under the root node.

getting started google cloud platform account

And then define the Credentials Mode, which defines how the credentials will be provided.

In all cases, the credential represents the JSON private key file containing the access token, which can be generate from Google Cloud Platform’s by administrators.

The following modes are available.

Name Description


When using this mode, the credentials will try to be retrieved automatically by Google APIs.

They will first be searched from an environment variable named GOOGLE_APPLICATION_CREDENTIALS.
If the environment variable does not exist, it will search in the current Google engine.

TIP: Refer to Authenticating as a service Google documentation for further details.


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.


JSon Access token string. This corresponds to the content of the JSON private key file corresponding to the account to connect with.

To fill this attribute, open your JSON private key file, copy its content and paste it in the attribute.

The benefit 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 applicationDefault or LocalFile modes for production environments.

Here is an example of JSON credential file:

  "type": "service_account",
  "project_id": "mygoogleproject",
  "private_key_id": "myprivatekey",
  "private_key": "myprivatekeyvalue",
  "client_email": "myaccountemail",
  "client_id": "myclientid",
  "auth_uri": "",
  "token_uri": "",
  "auth_provider_x509_cert_url": "",
  "client_x509_cert_url": "mycerturl"

Example with application default

getting started google cloud platform mode 1

Example with local file

getting started google cloud platform mode 2

Example with string

getting started google cloud platform mode 3

Next steps

Your Google Cloud Project Metadata is now ready.

You can start using it in related Google Cloud Platform technologies, such as Google Cloud Storage.

Sample Project

The Google Cloud Platform Component ships sample project(s) that contain various examples and use cases.

You can have a look at these projects to find samples and examples describing how to use it.

Refer to Install Components to learn how to import sample projects.