Added support for Google Cloud Functions #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
That's an awesome contribution. Thanks a lot! Would you mind adding a little section to the README on how to use this for GCP? |
|
Just added the requested docs update @schickling :)! |
|
Just release a new version! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Google provider will use the entrypoint not from the definition of the handler function, but instead from the package.json:main field, or via a
index.jsfile (See Google Cloud Docs for a reference).This change modifies the behaviour of the
extractFileNamesto enforce only discovery of those entry points that are used by the Google Cloud Functions runtime.These changes are backwards compatible with any existing AWS provider.