'Ello all, back to using Pulumi here and ran into ...
# python
'Ello all, back to using Pulumi here and ran into this weirdness when trying to update my Pipenv/lock/virtualenv. Did something change with the
python package behavior where it goes off and tries to install a provider automatically?
Copy code
[pipenv.exceptions.InstallError]:           check_call(['pulumi', 'plugin', 'install', 'resource', 'aws', PLUGIN_VERSION])
[pipenv.exceptions.InstallError]:         File "/opt/homebrew/Cellar/python@3.9/3.9.15/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 373, in check_call
[pipenv.exceptions.InstallError]:           raise CalledProcessError(retcode, cmd)
[pipenv.exceptions.InstallError]:       subprocess.CalledProcessError: Command '['pulumi', 'plugin', 'install', 'resource', 'aws', '5.16.0']' returned non-zero exit status 126.
[pipenv.exceptions.InstallError]:       [end of output]
[pipenv.exceptions.InstallError]:   note: This error originates from a subprocess, and is likely not a problem with pip.
[pipenv.exceptions.InstallError]: error: legacy-install-failure
[pipenv.exceptions.InstallError]: × Encountered error while trying to install package.
[pipenv.exceptions.InstallError]: ╰─> pulumi-aws
^ Ignore this, turns out I was shimming pulumi through asdf-vm plugin, and forgot to set the version globally so I was getting an error about that.. red herring!