sparse-intern-71089
07/18/2019, 8:58 PMswift-painter-31084
07/18/2019, 9:00 PMcolossal-beach-47527
07/18/2019, 9:41 PMcolossal-beach-47527
07/18/2019, 9:42 PMfuture-traffic-93788
07/18/2019, 9:45 PMfuture-traffic-93788
07/18/2019, 9:46 PMfuture-traffic-93788
07/18/2019, 9:46 PM/github/home/.kube/config
future-traffic-93788
07/18/2019, 9:46 PM72131f5ef143: Pull complete
Digest: sha256:69a8de9ddede0bafc40c7c7364b464e51cff19f038fd065c95dd05550c14a0c5
Status: Downloaded newer image for pulumi/actions:latest
Logging in using access token from PULUMI_ACCESS_TOKEN
### FAILED Pulumi Deploy (Current Stack) 21:39:42Z (54.643s)
future-traffic-93788
07/18/2019, 9:47 PMcolossal-beach-47527
07/18/2019, 9:47 PMfuture-traffic-93788
07/18/2019, 9:48 PMcolossal-beach-47527
07/18/2019, 9:50 PM.pulumi/ci.json
file?future-traffic-93788
07/18/2019, 9:50 PMcolossal-beach-47527
07/18/2019, 9:53 PMpulumi stack ls
/ pulumi stack select
. Though I’d need to review the source code for the Pulumi GitHub Actions container to see what it does. (Perhaps if there is only a single stack for the current project, it just uses that.)
Similarly, it might be worth double checking that the Pulumi.yaml
file is in the root of the repository? Or if a PULUMI_ROOT
environment variable is needed.future-traffic-93788
07/18/2019, 9:56 PMfuture-traffic-93788
07/18/2019, 9:56 PMfuture-traffic-93788
07/18/2019, 9:56 PMPULUMI_ACCESS_TOKEN
) or the .pulumi directorycolossal-beach-47527
07/18/2019, 9:59 PMPULUMI_ACCESS_TOKEN
environment variable for the GitHub actions? Or are you talking about the Pulumi app itself?future-traffic-93788
07/18/2019, 10:00 PMfuture-traffic-93788
07/18/2019, 10:00 PMfuture-traffic-93788
07/18/2019, 10:00 PMfuture-traffic-93788
07/18/2019, 10:02 PMfuture-traffic-93788
07/18/2019, 10:03 PMcolossal-beach-47527
07/19/2019, 1:12 AMpulumi
command-line tool, is installed. But when running your Python-based Pulumi program, the “pulumi” Python library isn’t found. (And you’d need to run pip
or something to have it installed.) This sounds like something that we could try to do automatically (e.g. run pip install
automatically to ensure all dependencies are available?) This should be easy to address by running some step before you invoke Pulumi in your GitHub Actions workflow. I’ll ask around and see if there is something in the works to make this more transparent, but at the very least I’ll file an issue to make sure we update the documentation to include steps for how to do this sort of thing when using Python.future-traffic-93788
07/19/2019, 3:54 PM