Deploying with a ZIP file
This section contains the steps to install a function without granting your Google Cloud project permissions directly in Function Store and do it by downloading a ZIP file.
Last updated
This section contains the steps to install a function without granting your Google Cloud project permissions directly in Function Store and do it by downloading a ZIP file.
Last updated
Function Store gives you alternatives to deploy a function:
Directly into the app, with a project you previously set up. Then, in a few steps, you add the necessary information about the function and install it.
Manually in GCP by uploading a ZIP file that includes all source files necessary for your function deployment, and following a considerable number of steps.
Although you need to go through more steps and a solid understanding of GCP is a must, manual installation with a ZIP file is an attractive option if:
You want to deploy your function without granting your GCP project permissions directly in Function Store.
You want to deeply understand the whole process that is running in the background.
The following steps guide you through the process of installing a function manually in GCP by uploading a ZIP file. In this case, it's a trigger type HTTPS function named universalWebhook:
In the GCP Console, go to the Cloud Functions page.
In the resource selector, select the project name or organization. Make sure that the project to which you want to install the ZIP is selected.
In the main content area, click the Create function button.
The name does not necessarily have to match the name of the Function Store function that you want to install.
In the Authentication field, select your desired authentication. If you want to create a public API, select the option Allow unauthenticated invocations. Otherwise, use the default settings to require authentication for your function. Click Save to save your changes.
In the Runtime environment variables, click the Add variable button. You must add the environment variables of the function.
The first one is the GCLOUD_PROJECT. Its value must be the current GCP project ID. Note that the project ID is not the name of the project. To make the process easier, the other environment variables you need are listed so you can copy and paste the name.
In the Runtime field, select the runtimeNode.js 10 for the function. In the Entry point field, write “handler” because this one is what the system uses by default.
Download the ZIP that contains all the elements of the function.
Click Browse in the ZIP file field to upload the function ZIP file from your local file system.
Your code will be staged in this Cloud Storage bucket as part of the deployment.
Your new function is listed on the Functions page. When the deployment is complete, a checkmark appears next to the function.
Note that some steps would change depending on the trigger type of the function, but don't worry, we have covered these changes in Function Store.
