This message was deleted.

/usr/bin/pulumi-language-python-exec

<= where is this file coming from…? It’s not in my image. I’m installing to

~/.pulumi/bin

and wrappers in

/usr/local/bin

…

Just catching up with what's going on here...

pulumi-language-python-exec

should be installed along with the pulumi python SDK when you run

poetry install

for your project.

Hmm isn’t that installed by

curl -fsSL <https://get.pulumi.com/> | bash -s -- --version $PULUMI_VERSION

I believe that only installs the Pulumi CLI thinking taco - I'm not 100% on that though

I install the CLI during my docker build….

the deploy executor uses automation api and calls out to the pulumi on path.

Is there any way I can see the source for

curl -H "Authorization: token $PULUMI_ACCESS_TOKEN" "$PULUMI_SERVICE_URL/preview/deployments/executor" |gzip -d >/pulumi-deploy-executor && chmod +x /pulumi-deploy-executor

backing up, is the issue here the

ModuleNotFoundError: No module named pulumi

?

yeah, I’m trying to use poetry

okay yeah, i'm following now. so that's because the deployment executor is using automation api to run the program, and the program doesn't know about where the poetry env is. interesting.

I tried to write a wrapper:

#!/bin/bash

for file_path in ~/.pulumi/bin/*; do
  file_name=$(basename "$file_path")
  wrapper_path="/usr/bin/$file_name"

  cat <<EOF > "$wrapper_path"
#!/bin/bash
echo poetry run "$file_path" "\$@"
EOF

  chmod +x "$wrapper_path"
done

I think maybe

poetry run

should wrap

/pulumi-deploy-executor

instead?

potentially… but the deployment executor gets downloaded into the container at runtime

yah - i appreciate all the effort you're putting into this and definitely want this to be a better experience for you! i'm following up internally to see what else I can find

❤️ thank you so much for all your help @red-match-15116!!

Is this helpful to you? https://github.com/ringods/pulumi-python-poetry-monorepo

ahh interesting, thank you, @limited-rainbow-51650!