In this case, we are going to leave the default option (HTTPS) and select the option mark as allow unauthenticity invocations . It is worth noting that this must be chosen carefully, as it is perfectly valid for demonstration purposes.
With your function and it
The correct option when you want to implement some kind of publicly accessible API, but depending on the nes and the environment in which the function is execut, you may be more interest in the second option ( require authentication ) and thus limit its scope.
Once we have select the trigger type
We will adjust the amount of memory that our function will use in the following section:
As it is a simple function, we will choose the minimum amount of memory available ( 128 MB ). We will not touch the rest of the options. If we click band database on the button mark NEXT we can configure the code for our function.
The first thing we ne to do is select
The execution environment we are going to use. In this case, and using the first drop-down list, we select Python (whose latest version as a separate category available at the time of writing this article is 3.12 ).
We have three options to specify
The code for our function: using the online itor (the interface we are using right now), uploading a .zip file from our computer, or doing the same (uploading a .zip file ) from Cloud Storage. In this case, we are going to leave the default option (using the online itor).
The last option we ne
To pay attention to (but we won’t modify it for this example) is the name of the entry point. The entry point is the function or code fragment that will be execut when our function is call. In this case, and having chosen HTTPS as the trigger, the entry point tg data will be call, as a guide, hello_http . We leave it as is.