Skip to main content
Version: 0.68.4

Plan

The plan object contains all enclave-modifying methods like add_service, remove_service, upload_files etc; for more look into Starlark instructions. All of the methods that come with the plan add to the list of instructions that Kurtosis would eventually execute in the Execution phase of the multi-phase run.

The plan object is the first object that gets injected into the run method in the main.star of your package or your standalone script. The package or script author must ensure that the first argument is an argument called plan, and then use the enclave-modifying functions from it. The author also must pass the plan methods down to any other scripts or packages that require enclave-modifying functions.

Here's an example :-

Imagine you have a kurtosis.yml that looks like

name: "github.com/test-author/test-package"

Further with a main.star at the root of the package that looks like

datastore = import_module("github.com/test-author/test-package/lib/datastore.star")

def run(plan):
datastore.create_datastore(plan)

and the lib/datastore.star looks like

def create_datastore(plan):
plan.add_service(
service_name = "datastore-service",
config = ServiceConfig(
image = "kurtosistech/example-datastore-server"
)
)

To accept arguments in the run function, pass them as the second parameter like so

def run(plan, args):
pass
caution

Any value returned by a plan function is a future-reference. This means that you can't run conditionals or interpretation time methods like string.split on it.