Creating a function version
To create a function version, you can use one of the code upload formats. A ZIP archive will be used for the example.
Warning
Files larger than 3.5 MB should be uploaded via Object Storage. For more information about limits, see Quotas and limits in Cloud Functions.
Preparing a ZIP archive with the function code
-
Save the following code to a file named
index.js
:exports.handler = async function (event, context) { let name = 'World'; if (event.queryStringParameters && event.queryStringParameters.name) { name = event.queryStringParameters.name } return { 'statusCode': 200, 'headers': { 'Content-Type': 'text/plain' }, 'isBase64Encoded': false, 'body': `Hello, ${name}!` } };
-
Add the
index.js
file into thehello-js.zip
ZIP archive.Note
If you use the Finder context menu to create a ZIP archive on macOS, a service directory titled
__MACOSX
is automatically added to the archive. This directory may cause errors when you build functions. To delete this directory from your ZIP archive, use the command line to navigate to the folder containing the archive and run this command:zip -d <archive_name>.zip "__MACOSX/*"
Creating a function version
When creating a version, set the following parameters:
- Runtime environment: Provides additional libraries and environment variables that can be accessed from the function code. It corresponds to the programming language your function is written in. For more information, see Runtime environment.
- Entry point: Function to be invoked as a handler.
- Timeout: Maximum function execution time, after which the service will terminate its execution without waiting for a response. It includes the time of the first initialization when the function is first run.
- In the management console
, select the folder containing the function. - Select Cloud Functions.
- Select the function to create a version of.
- Under Last version, click Сreate in editor.
- Select the runtime environment. Disable Add files with code examples.
- Click Continue.
- Prepare the function code:
- Runtime environment:
nodejs18
- Method:
ZIP archive
- File:
hello-js.zip
- Entry point:
index.handler
- Runtime environment:
- Set the version parameters:
- Timeout:
5
- Memory:
128 MB
- Service account:
Not selected
- Environment variables:
Not selected
- Timeout:
- Click Save changes.
If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID>
command. You can also set a different folder for any specific command using the --folder-name
or --folder-id
parameter.
To create a function version, run the command:
yc serverless function version create \
--function-name=my-nodejs-function \
--runtime nodejs18 \
--entrypoint index.handler \
--memory 128m \
--execution-timeout 5s \
--source-path ./hello-js.zip
Where:
--function-name
: Name of the function whose version you want to create.--runtime
: Runtime environment.--entrypoint
: Entry point in the following format:<file_name_without_extension>.<listener_name>
.--memory
: Amount of RAM.--execution-timeout
: Maximum function running time before timeout.--source-path
: ZIP archive with the function code and required dependencies.
Result:
done (1s)
id: d4evvn8obisa********
function_id: d4elpv8pft63********
created_at: "2020-08-01T19:09:19.531Z"
runtime: nodejs18
entrypoint: index.handler
resources:
memory: "134217728"
execution_timeout: 5s
image_size: "4096"
status: ACTIVE
tags:
- $latest
log_options:
folder_id: b1g681qpemb4********
With Terraform
Terraform is distributed under the Business Source License
For more information about the provider resources, see the relevant documentation on the Terraform
If you do not have Terraform yet, install it and configure the Yandex Cloud provider.
To create a new function version:
-
Open the Terraform configuration file and change the function parameters:
yandex_function
: Description of the function being created and its source code.name
: Function name.description
: Text description of the function.user_hash
: Any string to identify the function version. When the function changes, update this string, too. The function will update when this string is updated.runtime
: Function runtime environment.entrypoint
: Function name in the source code that will serve as an entry point to applications.memory
: Amount of memory allocated for the function, in MB.execution_timeout
: Function running timeout.service_account_id
: ID of the service account you want to use to invoke the function.content
: Function source code.content.0.zip_filename
: Name of the ZIP archive containing the function source code.
Here is an example of the configuration file structure:
resource "yandex_function" "test-function" { name = "test-function" description = "Test function" user_hash = "first-function" runtime = "nodejs18" entrypoint = "main" memory = "128" execution_timeout = "10" service_account_id = "<service_account_ID>" content { zip_filename = "<path_to_ZIP_archive>" } }
Note
If the function name or description is changed, the version will not be created.
For more information about
yandex_function
properties, see the relevant provider documentation . -
Check the configuration using this command:
terraform validate
If the configuration is correct, you will get this message:
Success! The configuration is valid.
-
Run this command:
terraform plan
You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will show them.
-
Apply the changes:
terraform apply
-
Type
yes
and press Enter to confirm the changes.
You can check the new version using the management console
yc serverless function version list --function-name <function_name>
To create a function version, use the createVersion REST API method for the Function resource or the FunctionService/CreateVersion gRPC API call.
Request example
To use the examples, install cURL
Example where code is fetched from an Object Storage bucket
-
Upload the
hello-js.zip
archive with the function version code to your Object Storage bucket. -
Prepare a file named
body.json
with the following request body:{ "functionId": "<function_ID>", "runtime": "nodejs22", "entrypoint": "index.handler", "resources": { "memory": "134217728" }, "executionTimeout": "5s", "serviceAccountId": "<service_account_ID>", "package": { "bucketName": "<bucket_name>", "objectName": "hello-js.zip" }, }
Where:
functionId
: ID of the function the version of which you want to create.runtime
: Runtime environment.entrypoint
: Entry point in the following format:<file_name_without_extension>.<listener_name>
.memory
: Amount of RAM.executionTimeout
: Maximum function running time before timeout.serviceAccountId
: ID of the service account with a role that allows bucket data reads.bucketName
: Name of the bucket where you uploaded the ZIP archive with the function code and required dependencies.objectName
: Key of the bucket object that contains the function code.
Example where code is provided in the request body
-
Encode the ZIP archive with the function code into Base64 format:
base64 -i hello-js.zip > output.txt
-
Prepare a file named
body.json
with the following request body:{ "functionId": "<function_ID>", "runtime": "nodejs22", "entrypoint": "index.handler", "resources": { "memory": "134217728" }, "executionTimeout": "5s", "content": "<ZIP_archive_contents_in_Base64_encoding>" }
Where:
functionId
: ID of the function the version of which you want to create.runtime
: Runtime environment.entrypoint
: Entry point in the following format:<file_name_without_extension>.<listener_name>
.memory
: Amount of RAM.executionTimeout
: Maximum function running time before timeout.content
: Function version code in Base64 encoding,output.txt
file contents.
Example where code is fetched from another function version in Cloud Functions
Prepare a file named body.json
with the following request body:
{
"functionId": "<function_ID>",
"runtime": "nodejs22",
"entrypoint": "index.handler",
"resources": {
"memory": "134217728"
},
"executionTimeout": "5s",
"versionId": "<previous_function_version_ID>"
}
Where:
functionId
: ID of the function the version of which you want to create.runtime
: Runtime environment.entrypoint
: Entry point in the following format:<file_name_without_extension>.<listener_name>
.memory
: Amount of RAM.executionTimeout
: Maximum function running time before timeout.versionId
: ID of a previous function version.
Send the request by specifying the path to the previously prepared file with the request body:
export IAM_TOKEN=$(yc iam create-token)
curl -X POST \
-H "Authorization: Bearer ${IAM_TOKEN}" \
-d "@<body.json_file_path>" \
https://serverless-functions.api.cloud.yandex.net/functions/v1/versions
Result:
{
"done": false,
"metadata": {
"@type": "type.googleapis.com/yandex.cloud.serverless.functions.v1.CreateFunctionVersionMetadata",
"functionVersionId": "d4e25m0gila4********"
},
"id": "d4edk0oobcc9********",
"description": "Create function version",
"createdAt": "2023-10-11T11:22:21.286786431Z",
"createdBy": "ajeol2afu1js********",
"modifiedAt": "2023-10-11T11:22:21.286786431Z"
}
You can create a function version using the Yandex Cloud Toolkit plugin
Note
To ensure the integrity of version links, you cannot update function versions. For more information about the resource relationships, see Function.