Ok so it’s me again… posted in #getting-started before not realizing this channel exists… I’m trying to get deployments to run with Poetry. I’d like to not specify

runtime:
  name: python
  options:
    virtualenv: venv

in my Pulumi.yaml because locally we use

poetry run pulumi up

and poetry uses the correct virtualenv automatically. Side note: we are using a custom docker image for deployments because we’re using python 3.10 so I built one:

# based on <https://github.com/pulumi/pulumi-docker-containers/blob/main/docker/pulumi/Dockerfile>

FROM python:3.10-slim

RUN apt-get update -y && \
  apt-get install -y \
  curl

# Passing --build-arg PULUMI_VERSION=vX.Y.Z will use that version
# of the SDK. Otherwise, we use whatever <http://get.pulumi.com|get.pulumi.com> thinks is
# the latest
ARG PULUMI_VERSION

# Install the Pulumi SDK, including the CLI and language runtimes.
RUN curl -fsSL <https://get.pulumi.com/> | bash -s -- --version $PULUMI_VERSION

# Install Poetry
ENV POETRY_HOME=/usr/local
RUN curl -sSL <https://install.python-poetry.org> | python3 -

# Create wrappers such that pulumi commands always run with poetry
COPY ./create-poetry-wrappers.sh /usr/local/bin
RUN create-poetry-wrappers.sh

ENTRYPOINT ["/bin/bash", "-c"]
CMD [ "/bin/bash" ]

I thought that I could create some wrapper scripts to force

poetry run …

on pulumi, but it seems like the

/pulumi-deploy-executor

is not ? somehow? using the pulumi located in the container’s $PATH?

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!