I have another question. I'm not sure if I'm just "doing it wrong" but I would expect this to output "my host is: <hostname>" but the value for the hostname is empty:

pulumi env run myorg/databricks-foo -- echo "my host is: $DATABRICKS_HOST"

considering my environment looks like this:

values:
      databricks:
        host: https://<hostname here>
      environmentVariables:
        DATABRICKS_HOST: ${databricks.host}
      pulumiConfig:
        databricks:host: ${databricks.host}

when I run:

eval `pulumi env get myorg/databricks-foo --value shell`

and then

echo "my host is: $DATABRICKS_HOST"

I get the expected output. I would expect

pulumi env run

to make the env vars available to the command its running, but that's not the behavior I'm seeing.

Are you running this from the shell?

yeah, I'm using zsh

So you'll need to quote things appropriately so that zsh doesn't do that work.

hmm, even when do

pulumi env run myorg/env -- echo "host: ${DATABRICKS_HOST}"

?

Yes, that won't work, because double-quoted strings are parsed by the current shell. The value has already been substituted before the shell invokes pulumi.

for now, I'm just doing

eval `pulumi env run ... --value shell`

which works

Yes, because the env var isn't being substituted by your interactive shell

Can you try escaping the dollar,

$$DATABRICKS_HOST

it's weird because I can do the same thing with tools like chamber and don't have the same issue. Like this.

Which example on that page?

sorry, I was trying to link to the section on

Exec

In zsh isn't the escape

\$

? Or you could turn your double-quotes into single-quotes. I'm not optimistic though, since prevent the outer shell parsing the var would presumably also prevent the pulumi-spawned shell from doing it.

when I do the double-dollar it looks like the first

$

is being sub'd w/ the proc:

my host is 38389{DATABRICKS_HOST}

Yes,

$$

is wrong.

It depends how pulumi is running the command. If they're wrapping in a shell, single quotes will work (or escaping). Otherwise, you'll need to wrap the command with

sh -c 'your command here'

what I'm saying is that when I run

chamber exec <ns> -- echo "my host is $DATABRICKS_HOST"

I get the expected output

Yes, if evaluating the escaped values "unescapes" them for the next shell, that would be good.

I've made sure to

unset DATABRICKS_HOST

Then I don't know how that works. It defies my knowledge of shells and parsing. I know it would work if it was being run from something other than an interactive shell (I do that sort of thing in my package.json files all the time), but once the interactive shell gets involved, the rules change.

yep, that works

Which, wrapping in

sh -c

?

yeah, wrapping in

sh -c

-- this:

pulumi env run myorg/myenv -- sh -c 'echo my host is: $DATABRICKS_HOST'