Dependencies¶
For general information on dependency management in FunctionGraph, see also:
Introduction¶
A dependency contains public libraries that support the running of function code. You can encapsulate the required public libraries into a dependency for easier management, sharing, and smaller deployment sizes.
You can keep multiple versions of the same dependency for systematic management.
Besides dependencies, FunctionGraph includes a number of bundled libraries included in the runtime environment, which are available for use without the need for packaging them into a dependency. These bundled libraries are pre-installed and maintained by FunctionGraph, and they provide commonly used functionalities that can be used directly in your function code. For more information, see Bundled Libraries. If you want to use a different version of a runtime-included library, you can do this by bundling it with your function in your deployment package or by adding it as a dependency.
Notes and Constraints¶
The maximum size of a private dependency is 300 MB, and the maximum number of files in a dependency is 30,000. For dependencies greater than 300 MB, you need to split and upload them as multiple dependencies, and then specify multiple dependencies for a function.
The name of a file in a dependency cannot end with a tilde (~), for example, module~.
A maximum of 20 dependencies can be specified for a function.
Dependencies in use cannot be deleted.
Dependencies are merged with the function code. If a dependency contains a file with the same name as a file in the function code, the file in the dependency takes precedence over the file in the function code. Therefore, do not use dependencies to package files that have the same names as files in the function code.