Added support for entryPoint option, to explicitly define the exporte… #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…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
:would be dynamically changed by my plugin to:
Since Google defaults the
entryPoint
to be the same as ourhandler
, the deployment was always ending with an error saying that my exported functiondevelop-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
)