Deploy a Custom Function to Data 360 Sandbox by Using CLI
The deployment uploads the code package to Data 360. After deployment, your function is available as a chunking strategy option in the search index builder.
| Edition Table |
|---|
| Available in: Developer, Enterprise, Performance, and Unlimited Editions. See Data 360 edition availability. |
| User Permissions Needed | |
|---|---|
| To deploy a custom function and use it for search index chunking: | Permission set:
|
- Write your custom chunking function and validate it locally. See Write a Custom Chunking Function.
-
Open a terminal, and go to the root of your code extension function package (the folder that contains
payload/). -
Make sure that you are signed in to the target org.
-
Refresh package metadata from the package root.
-
Deploy your code extension function.
Example:
-
--name <DEPLOYMENT_NAME>(required): Name for your code extension deployment. -
--package-version <PACKAGE_VERSION>(required): Semantic version for the package (for example,1.0.0). -
--description "<DESCRIPTION>"(required): Short description of the deployment. -
--package-dir ./payload(required): Directory that contains your packaged function (typically./payloadunder the package root). -
--target-org <ORG_ALIAS>(required): Org username or alias (same as othersfcommands). -
--cpu-size(optional): The CPU size:CPU_L,CPU_XL,CPU_2XL(default), orCPU_4XL. Larger sizes provide more processing power but consume more credits. To understand how the compute size affects the compute model and credit consumption, see Salesforce Help: Billing Considerations for Code Extension. -
--network(optional): Network setting for packages that include Jupyter notebooks (for example,hostfor host network mode).Example:
- Confirm that the code deployment is successful. See Monitor Custom Function Deployments.