In order to create a snap-in version, functions must be defined as shown in the code samples. Functions are packaged and provided as an artifact at the time of snap-in version creation and then used to deploy functions to snap-in versions. An artifact may contain multiple function definitions. The artifact is a zip file containing the following files:
1 /2 ├── src/3 ├ ├── functions/ # Contains a folder each for the functions defined in the manifest. The folder name should match the function name in manifest.4 ├ ├── functions/function-1/ # function-1 is a function defined in the manifest.5 ├ ├── function-factory.ts # defines the functions to be imported. Each function to be used in the manifest should be included here. Refer to the example for the format.6 ├── dist/ # Contains the transpiled code for the functions. Autogenerated but should be included in the artifact.7 ├── package.json # Contains the dependencies for the functions.
The function manifest consists of the following fields:
1 functions:2 - name: function_13 description: Function 1
- name: It is the function name that should match the corresponding function name in the folder.
- description: It describes the function.
Refer to the function invocation for details about the exact payload of the function.