Support serviceAccount option for deployment

[xyi]

[vranystepan]

Cool! I hope it'll be merged soon :+1:

[davidjb99]

This is exactly what I wanted, would be great to get it merged!

[paulotokimatu]

Related to #161

@pmuens Do you think this good to go?

[jorgejch]

Anxious to see this in.

[jorgejch]

btw, tested. works.

functions:
  first:
    serviceAccount: account_email
    ...

[luisgreen]

Do we have an ETA for merge?? I'm really wanting this feature :)

[jamestjw]

This feature is super desirable, really need this.

[shaharappload]

This pull request doesn't work anymore, becuase it's now called serviceAccountEmail in GCP Cloud Functions JSON/YAML payload.

You can use serverless-google-cloudfunctions-amazing npm package based on serverless-google-cloudfunctions-awsome with some advanced features that are not supported yet in serverless-google-cloudfunctions package.

Usage example (using variable reference):

functions:
  example:
    serviceAccount: ${self:custom.serviceAccount.${self:provider.stage}}

OR

functions:
  example:
    serviceAccount: [email protected]

[GerardPaligot]

After one year, there is always interested people about this feature in the SF GCP plugin (including me). The project of @shaharappload is interesting but that could be great to add this kind of feature natively in the plugin. If I create a new PR for this, it will be reviewed?

[davedc]

@GerardPaligot was looking to make a patch with this. Found that this was already merged here.

functions:
  a-function:
    serviceAccountEmail: [email protected]