This introduction will guide you through the quickstart process for setting up and deploying your first Cloud Function, enabling you to kickstart your serverless journey with ease. To begin, ensure you have a GCP account and have installed the Google Cloud SDK on your local machine. With these prerequisites met, you can proceed to create your first Cloud Function.<\/p>\r\n
Prerequisites<\/h2>\r\n\r\n- A Google Cloud Platform account<\/li>\r\n
- A project with billing enabled, since Cloud Run functions requires it even within the free tier<\/li>\r\n<\/ul>\r\n
Step by Step Process of Cloud Function Quickstart<\/h2>\r\nStep One: Open the Functions Section<\/h3>\r\n
From the Cloud Console, open the menu and go to the Cloud Functions, or Cloud Run functions, section.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-668.png\")
<\/figure>\r\n\r\n\r\n\r\nStep Two: Create a Function<\/h3>\r\n
Click Create function to begin.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-669.png\")
<\/figure>\r\n\r\n\r\n\r\nStep Three: Name Your Function and Choose a Region<\/h3>\r\n
Give the function a name and pick the region it should run in. If the console offers a choice between generations here, choose the current generation, previously called 2nd gen, unless you specifically need the older first generation for compatibility reasons.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-670.png\")
<\/figure>\r\n\r\n\r\n\r\nStep Four: Choose the Trigger Type<\/h3>\r\n
Choose HTTP as the trigger type for this example. You will also see an option for authentication. If you tick Require authentication<\/b><\/strong>, only callers with the right permissions can invoke the function. If you leave it unticked, or explicitly allow unauthenticated invocations depending on how your console presents this option, anyone with the URL can call it, which is the simpler choice while you are just testing. Click Save once you have made your choice.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-671.png\")
<\/figure>\r\n\r\n\r\n\r\nStep Five: Confirm the Trigger<\/h3>\r\n
The trigger will be created. Click Next to continue to the function’s code.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-672.png\")
<\/figure>\r\n\r\n\r\n\r\nStep Six: Choose a Runtime and Add Your Code<\/h2>\r\n
In the configuration step, choose your runtime. This example uses Node.js, and the entry point needs to match the exported function name exactly, helloWorld in this case.<\/p>\r\n
exports.helloWorld = (req, res) => {
\u00a0\u00a0let message = req.query.message || req.body.message || “Hello World!”;
\u00a0\u00a0res.status(200).send(message);
};<\/p>\r\n
Once your code is in place, click Deploy.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-673.png\")
<\/figure>\r\n\r\n\r\n\r\nStep Seven: Open Your Deployed Function<\/h3>\r\n
Once deployment finishes, open the function you just created from the functions list.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-674.png\")
<\/figure>\r\n\r\n\r\n\r\nStep Eight: Test the Function<\/h3>\r\n
Click the Testing tab. The triggering event is shown here, ready for you to run against your function.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-675.png\")
<\/figure>\r\n\r\n\r\n\r\nClick Test the function, and the output will be shown directly below.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/prwatech.in\/blog\/wp-content\/uploads\/2021\/05\/image-676.png\")
<\/figure>\r\n <\/p>\r\n
First Generation Compared to the Current Generation<\/h2>\r\n
The older first generation, now labeled Cloud Run functions (1st gen), has a maximum execution time of 9 minutes and a narrower set of supported event sources. The current generation is built directly on Cloud Run and Eventarc, giving you a longer execution window, broader event source support, and the same performance and scaling controls Cloud Run services get, since a function deployed this way is, under the hood, running as a Cloud Run service. Unless you have an existing first generation function you need to keep compatible with something else, current guidance is to build new functions on the current generation by default.<\/p>\r\n
Common Mistakes to Avoid<\/h2>\r\n
Step by Step Process of Cloud Function Quickstart<\/h2>\r\nStep One: Open the Functions Section<\/h3>\r\n
From the Cloud Console, open the menu and go to the Cloud Functions, or Cloud Run functions, section.<\/p>\r\n\r\n\r\n\r\n Click Create function to begin.<\/p>\r\n\r\n\r\n\r\n Give the function a name and pick the region it should run in. If the console offers a choice between generations here, choose the current generation, previously called 2nd gen, unless you specifically need the older first generation for compatibility reasons.<\/p>\r\n\r\n\r\n\r\n Choose HTTP as the trigger type for this example. You will also see an option for authentication. If you tick Require authentication<\/b><\/strong>, only callers with the right permissions can invoke the function. If you leave it unticked, or explicitly allow unauthenticated invocations depending on how your console presents this option, anyone with the URL can call it, which is the simpler choice while you are just testing. Click Save once you have made your choice.<\/p>\r\n\r\n\r\n\r\n The trigger will be created. Click Next to continue to the function’s code.<\/p>\r\n\r\n\r\n\r\n In the configuration step, choose your runtime. This example uses Node.js, and the entry point needs to match the exported function name exactly, helloWorld in this case.<\/p>\r\n exports.helloWorld = (req, res) => { Once your code is in place, click Deploy.<\/p>\r\n\r\n\r\n\r\n Once deployment finishes, open the function you just created from the functions list.<\/p>\r\n\r\n\r\n\r\n Click the Testing tab. The triggering event is shown here, ready for you to run against your function.<\/p>\r\n\r\n\r\n\r\n Click Test the function, and the output will be shown directly below.<\/p>\r\n\r\n\r\n\r\n <\/p>\r\n The older first generation, now labeled Cloud Run functions (1st gen), has a maximum execution time of 9 minutes and a narrower set of supported event sources. The current generation is built directly on Cloud Run and Eventarc, giving you a longer execution window, broader event source support, and the same performance and scaling controls Cloud Run services get, since a function deployed this way is, under the hood, running as a Cloud Run service. Unless you have an existing first generation function you need to keep compatible with something else, current guidance is to build new functions on the current generation by default.<\/p>\r\n<\/figure>\r\n\r\n\r\n\r\nStep Two: Create a Function<\/h3>\r\n
<\/figure>\r\n\r\n\r\n\r\nStep Three: Name Your Function and Choose a Region<\/h3>\r\n
<\/figure>\r\n\r\n\r\n\r\nStep Four: Choose the Trigger Type<\/h3>\r\n
<\/figure>\r\n\r\n\r\n\r\nStep Five: Confirm the Trigger<\/h3>\r\n
<\/figure>\r\n\r\n\r\n\r\nStep Six: Choose a Runtime and Add Your Code<\/h2>\r\n
\u00a0\u00a0let message = req.query.message || req.body.message || “Hello World!”;
\u00a0\u00a0res.status(200).send(message);
};<\/p>\r\n<\/figure>\r\n\r\n\r\n\r\nStep Seven: Open Your Deployed Function<\/h3>\r\n
<\/figure>\r\n\r\n\r\n\r\nStep Eight: Test the Function<\/h3>\r\n
<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\nFirst Generation Compared to the Current Generation<\/h2>\r\n
Common Mistakes to Avoid<\/h2>\r\n