witty-battery-24953
01/08/2020, 5:45 PMNo module named pulumi
error, but using the v1.7.1 tagged actions container works just fine. Unrelated question: where's the right place to bring up issues with actions/ci in general? Opening up an issue in the pulumi/pulumi
repo didn't seem quite right...colossal-beach-47527
01/08/2020, 5:50 PMpulumi/pulumi
repo is the right location, or mentioning it in the #python channel works too š
Iām taking a look now.pulumi/pulumi
container doesnāt install any dependencies before running. You would need to first run pip3 install
first, which would download all of the required dependencies.
The pulumi/actions
container (which is ~the same, but intended to be used for GitHub Actions) has a specialized entry point that looks for a package manager and triggers an install first.
https://github.com/pulumi/pulumi/blob/master/dist/actions/entrypoint.sh#L103pip install
and do not expect this error?
Also, how are you using the pulumi/pulumi
container?witty-battery-24953
01/08/2020, 5:53 PMpulumi/actions
container in a github actions spec (-Ā uses:Ā <docker://pulumi/actions>
) fails-Ā uses:Ā <docker://pulumi/actions:v1.7.1>
works.on: pull_request
name: Pulumi
jobs:
preview:
name: Preview
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
with:
fetch-depth: 1
- uses: <docker://pulumi/actions:v1.7.1> # <-- Dropping the version specifier here fails since v1.8.1 was pushed earlier today
env:
PULUMI_CI: pr
PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
with:
args: preview -s prod
colossal-beach-47527
01/08/2020, 5:58 PMactions.yaml
file, it will work for your Python app. Since pulumi/actions:v1.7.1
does all the things you need. But changing that to the latest pulumi/actions:v1.8.1
fails with the error you have above? āNo module named āpulumiāā? Do I have that all right?witty-battery-24953
01/08/2020, 5:59 PMpulumi/actions:latest
, it will fail with pulumi/actions
(so this impacts any actions.yaml
using Python that doesn't pin the pulumi/actions
version)entrypoint.sh
to try to help pin down the change that broke things, but I'm not sure what date I should be looking around...colossal-beach-47527
01/08/2020, 6:05 PMentrypoint.sh
file? If so, does it match what you see here on GitHub?
https://github.com/pulumi/pulumi/blob/master/dist/actions/entrypoint.shpulumi/actions
container does look like we have published the wrong one. (The entry point is probably the one from the pulumi/pulumi
container and not the pulumi/actions
container.) Iāll try to fix this ASAP.witty-battery-24953
01/08/2020, 6:09 PMpulumi/actions
image locally I'm not even seeing a /usr/bin/pulumi-action
filecolossal-beach-47527
01/08/2020, 8:12 PMpulumi/actions:v1.8.1
or pulumi/actions:latest
and have any problems please let me know!witty-battery-24953
01/08/2020, 8:48 PM