Pass env to run_sh

[barnabasbusa]

Background & motivation

It would be great if I could pass env variables to run_sh.

Desired behaviour

result = plan.run_sh(
        run = "mkdir -p kurtosis && echo $EXAMPLE",
        image = "badouralix/curl-jq",
        files = {
            "/path/to/file/1": files_artifact_1,
            "/path/to/file/2": files_artifact_2,
        },
        env = {
            "EXAMPLE": value
        },
        store = [
            # EXAMPLE: Creates a files artifact named `kurtosis_txt` containing the `kurtosis.txt` file
            StoreSpec(src = "/src/kurtosis.txt", name = "kurtosis_txt"),
            
            # EXAMPLE: Creates a files artifact with an automatically-generated name containing `genesis.json`
            StoreSpec(src = "/genesis.json"),

            # EXAMPLE: Creates a files artifact with an automatically-generated name containing `address.json`
            # This is just syntactic sugar for:
            # StoreSpec(src = "/coinbase/address.json")
            "/coinbase/address.json"
        ],
        wait="180s"
    )

How important is this to you?

Painful; the lack of this feature makes using Kurtosis frictionful.

What area of the product does this pertain to?

CLI: the Command Line Interface

[mieubrisse]

hey @barnabasbusa ! It's not an actual solution, but a workaround would be inlining the environment variable:

run="mkdir -p kurtosis && EXAMPLE=" + some_value + " echo $EXAMPLE"

[barnabasbusa]

my point would be to be able to inject a variable from outside.

somevalue = (1+2)
...
env ={EXAMPLE: somevalue}
...