Skip to content

Added support for entryPoint option, to explicitly define the exporte… #98

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wants to merge 1 commit into from

Conversation

markmssd
Copy link

…d function to use - defaults to handler's name.

Use case: I was trying to write another plugin that would dynamically change the gcloud function's name based on the CI branch. For example my serverless.yml:

functions:
  login:
    handler: login
    events:
      - http: path

would be dynamically changed by my plugin to:

functions:
  develop-login:
    handler: develop-login
    entryPoint: login
    events:
      - http: path

Since Google defaults the entryPoint to be the same as our handler, the deployment was always ending with an error saying that my exported function develop-login does not exist...

This PR allows us to explicitly set the entryPoint to each function (if not, it'll still default to the handler)

…d function to use - defaults to handler's name
@CaptainJojo
Copy link

Then a lot, that good :)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants