Custom name for Google Cloud Function

[peric]

Custom name for Google cloud functions

Description

For AWS lambda, it is possible to set custom name for a Lambda function (https://serverless.com/framework/docs/providers/aws/guide/functions/, line 14 in the example).

I want to be able to do the same with google provider, where config will look something like this:

functions:
  handler:
    handler: Handler
    name: BackupHandler
    memorySize: 256
    timeout: 300s

There are multiple reasons why this can be useful:

• better (and more descriptive) naming of google cloud functions. e.g. if you have multiple cloud functions in the same project, some are written in python and some in golang, you'll end up with names like backup_handler and BackupHandler
• if you have a package named backup, golint recommends you have a function named Handler and not BackupHandler. But if you deploy Handler to google cloud, it's just not descriptive enough

[cirdes]

There are two PR related to that one https://github.com/serverless/serverless-google-cloudfunctions/pull/97 and https://github.com/serverless/serverless-google-cloudfunctions/pull/98 that have been open almost one year ago.

I have 3 stages (dev, staging, production) and because of the entry point and function name share the same name I can't have 3 different functions. If I deploy with production it will subscribe dev.

[lucas-paes-movile]

Is someone ever going to consider this issue? It's been really annoying to deploy to different environments without being able to define function names.

[thucnc]

@pmuens may you take a look and do a merge for above PRs to release this feature ?

[joshuaquek]

Same issue as https://github.com/serverless/serverless-google-cloudfunctions/issues/84

Update: Posted a workaround solution on https://github.com/serverless/serverless-google-cloudfunctions/issues/84