This message was deleted.

I wish!

I have some experience, what are you trying to do?

@colossal-beach-47527 so I'm having trouble with deploying to kubernetes

Ugh. Yeah, I think there is an issue about the output of Pulumi being cut off in the event of a failure. Since obviously there isn’t any info to go on here. If you go to the Pulumi Cloud Console for the stack to update, do you see an update failure there? (And more importantly the specific logs for why the update failed.)

nope, no activity in pulumi cloud console

How are you specifying which stack you want to update as part of the GitHub Actions workflow? Off the top of my head I don’t recall the default to how the container image determines which stack to update. But perhaps this has to do with your

.pulumi/ci.json

file?

ok, I'll take a look at that then. How does pulumi normally determine stack when running locally?

Usually you’d run

pulumi 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.

so I don't have a ci.json atm. Added and seeing what happens.

What is confusing about that example? That the app is deployed by using a

PULUMI_ACCESS_TOKEN

environment variable for the GitHub actions? Or are you talking about the Pulumi app itself?

how it's being deployed and how it's finding the stack

Sorry for the delay in getting back to you. It looks like Pulumi, the

pulumi

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.

thanks. That and fixing the log output would be very helpful. I ended up having to fork the action to install pulumi python because running the install in a previous step was failing. (Also worrying is that all the standard python docker images I tried are unable to install pulumi_kubernetes. They fail with "pulumi is missing" )