This message was deleted.
# general
s
This message was deleted.
d
do you have an M1 mac? I had to do a few workaround to get it working there
w
I don't - it's a 2018 model, running i7
Has anyone got any thoughts on this? Still struggling to find out what’s happening.
w
Does
pulumi up --debug -v 9
show anything? Or is it hanging even before any of that output is shown? Otherwise, maybe reinstall using
brew
?
w
It hangs before any of the output is shown, unfortunately. I’ll uninstall and try with brew.
Uninstalled via
rm -rf ~/.pulumi/
and then started a new terminal session,
pulumi version
resulted with command not found, installed Pulumi via
brew install pulumi
, version check from
pulumi version
showed
v2.22.0
, running your command above (
pulumi up --debug -v 9
) still hangs - no output at all 😞
I have noticed in the past, when running
pulumi up
and leaving it for about 5 or more minutes, it does eventually come back with the response. But obviously that’s not ideal 😆
w
Are you using the Pulumi SaaS for state backend or your own?
w
We’re using S3
w
Regardless, maybe testing with local backend may shed some light on the matter:
Copy code
pulumi logout
pulumi login --local
<do the secrets stuff>
pulumi up
<any better?>
pulumi logout
w
I’ll give that a go, thanks!
I’ve seemed to be able to work around the problem.. it seems as though my problem was with python and the venv I had generated… I had to
pyenv install 3.7.9
and then copy the
~/.pyenv/version/3.7.9/
folder to my repo directory and rename it to
venv
, copy over a generic
venv/bin/activate
file, and then `pulumi foobar`… no idea why, not sure of the cause or the problem, but can only assume it’s something with my pyenv and the python namespace going all strange!
Thanks for your help 🙂
w
Yeah, Pulumi python does “default” to using virtualvenvs: https://www.pulumi.com/docs/intro/languages/python/ Regardless, glad you got it figured out.