Google - Functions

If you are using Google Cloud Functions as a provider, all functions inside the service are Google Cloud Functions.

Configuration

All of the Google Cloud Functions in your serverless service can be found in serverless.yml under the functions property.

# serverless.yml
service: my-gcloud-service

provider:
  name: google

plugins:
  - serverless-google-cloudfunctions

functions:
  first:
    handler: http
    events:
      - http: true

You can specify an array of functions, which is useful if you separate your functions in to different files:

# serverless.yml
---
functions:
  - ${file(./foo-functions.yml)}
  - ${file(./bar-functions.yml)}

# foo-functions.yml
getFoo:
  handler: handler.foo
deleteFoo:
  handler: handler.foo

Handler

The handler property should be the function name you've exported in your entrypoint file.

When you e.g. export a function with the name http in index.js your handler should be handler: http.

// index.js
exports.http = (request, response) => {};

A note about index.js and the entrypoint file

Google Cloud Functions assumes that you have a index.js or function.js file with the exported handler functions in the root of your project (you can read more about that in their docs).

However you can overwrite this by specifying the entrypoint file with the help of the main config parameter in the projects package.json file.

Our recommendation is to have an index.js file with all the function handlers in the projects root directory.

Memory size and timeout

The memorySize and timeout for the functions can be specified on the provider or function level. The provider wide definition causes all functions to share this config, whereas the function wide definition means that this configuration is only valid for the function.

The default memorySize is 256 and the default timeout is 60s if not specified.

# serverless.yml

provider:
  memorySize: 1024
  timeout: 90s

functions:
  first:
    handler: first
  second:
    handler: second
    memorySize: 512
    timeout: 120s

Environment variables

Google Cloud Functions support environment variables. Those can be useful in a lot of ways, especially when deploying across multiple environments. Environment variables are defined as key-value pairs.

The environment property can be specified at the provider or at the function level. The provider wide definition causes all functions to share those environment variables, whereas the function wide definition means that this configuration is only valid for the function.

By default, no environment variable is passed to the functions. All environment variable values must be strings.

# serverless.yml

provider:
  environment:
    max_delay: '5000'

functions:
  first:
    handler: first
  second:
    handler: second
    environment:
      auth_provider: oauth2

Handler signatures

Google Cloud Functions have different handler signatures dependent on the event type which will trigger them.

http events

exports.http = (request, response) => {
  response.status(200).send('Hello World!');
};

event events

exports.event = (event, callback) => {
  console.log('Hello World!');
  callback();
};

Labels

Google Cloud Platform supports labels to assist in organizing resources. Serverless allows you to define labels to be applied to functions upon deploy. Labels are defined as key-value pairs.

Labels can be applied globally, to all functions in your configuration file, and to specific functions.

There are limitations to labels. Make sure to consult the link above to learn about the requirements.

# serverless.yml

provider:
  name: google
  labels:
    application: serverless-example

functions:
  first:
    handler: httpFirst
    events:
      - http: true
    labels:
      team: gcf-team
  second:
    handler: httpSecond
    events:
      - http: true
    labels:
      application: serverless-example_documentation

With the above configuration the httpFirst function would have two labels applied, application and team. The value of the application label would be serverless-example, the value of the team label would be gcf-team.

The httpSecond function would have only one label applied, application, and it would have a value of serverless-example_documentation.

Labels defined under the provider object are applied to all functions in the file. Labels defined under specific functions only apply to that function. The labels defined under a function's object will override global labels for that function.