Create a Ray Function
Define a ray Function with its Python source, entrypoint and dependencies.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| project | str | (✓) | Project name. Required only when creating from the library; otherwise MUST NOT be set. |
| name | str | ✓ | Name that identifies the object. |
| kind | str | ✓ | Function kind. Must be ray. |
| uuid | str | Object ID in UUID4 format. | |
| description | str | Description of the object. | |
| labels | list[str] | List of labels. | |
| embedded | bool | Whether to embed the object in the project. | |
| code_src | str | URI pointing to the source code. | |
| code | str | Source code provided as plain text. | |
| base64 | str | Source code encoded as base64. | |
| handler | str | Function entrypoint. | |
| image | str | Container image used to execute the function. | |
| base_image | str | Base image (name:tag) used to build the execution image. | |
| requirements | list[str] | str | Python requirements or a supported requirements file path. | |
| ray_version | str | Ray version to use. |
Base image
The base image is the foundation used to build the execution image. Some base images may be restricted by cluster security policies; check with the cluster administrator.
Requirements
Requirements can be a list of strings or a path to requirements.txt, setup.py, pyproject.toml, conda.yml, or conda.yaml. The SDK parses requirements when saving the Function. If a package is available in the local environment without a version, the SDK may add its installed version; use explicit versions or constraints to avoid this inference.