-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloud Task + GAE + Functions Tutorial #1488
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This review covers everything up to but not including the function. As discussed in comments and in chat, I think there's some security/abuse issues that need sorting, and a number of other nits worth considering.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. I've added some comments and requested changes.
Can we have more of a PR description and background to this change? Any internal docs we can link for more background?
For example:
- Why do we need to use GAE and GCF together?
- How does this compare to other samples?
- Why was SendGrid chosen?
cloud-tasks/README.md
Outdated
|
||
Before you can deploy the sample, you will need to do the following: | ||
|
||
1. Enable the Cloud Function and Cloud Tasks APIs in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Please use direct links
- Please ensure the product names are correct (Cloud Functions)
Suggestion
1. [Enable](https://console.cloud.google.com/flows/enableapi?apiid=cloudfunctions.googleapis.com,cloudtasks.googleapis.com) the Cloud Functions and Cloud Tasks APIs
- Enable the Cloud Functions and Cloud Tasks APIs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I say, for example, "The Cloud Function does ..." or should I just say "The function does ..."?
env_vars: { | ||
key: "TRAMPOLINE_IMAGE" | ||
value: "gcr.io/cloud-devrel-kokoro-resources/node:10-user" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does cloud-tasks need a customized common.cfg? So far most products don't need one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Every folder in .kokoro
has a common.cfg
file, but you are right it is a duplication of the parents.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking my security feedback into account, things are looking good. I gave it another careful review and while I have a number of new comments, none of them seem like merge blockers: I'm comfortable with you merging without them or taking them as useful polish feedback.
return response.name; | ||
} catch (error) { | ||
// Construct error for Stackdriver Error Reporting | ||
console.error(Error(error.message)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-Blocking.
Did you end up confirming that console.error(error)
does not work?
It would be worth comparing the output from the two commands and seeing what the difference is, it might be fixable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did run some more isolated tests and console.error(error)
did not show up in Error Reporting.
You can fix the lint errors with |
No description provided.