https://pulumi.com logo
#general
Title
# general
f

fresh-daybreak-17893

01/28/2020, 10:29 PM
What is the officially supported (or at least most commonly recommended) way of downgrading the Pulumi command line tool? Motivation for asking: my team has been hit by the defect addressed in https://github.com/pulumi/pulumi/pull/3798. We would like all team members to have
pulumi preview
working on their workstations. This isn't currently the case since some team members have already upgraded to 1.9.1, which is the version exhibiting the unwanted behavior, while some others are on 1.8.1 which still works for our use case.
g

gentle-diamond-70147

01/28/2020, 10:40 PM
I believe 1.9.1 contains the fix for that particular regression. Are you sure you're still seeing that behavior in 1.9.1? https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md#191-2020-01-27
w

white-balloon-205

01/28/2020, 10:41 PM
The issue in https://github.com/pulumi/pulumi/pull/3798 should be addressed in 1.9.1 - so it may be you can roll forward to new versions? Note that that issue is also in the Python SDK, not in the
pulumi
CLI, so the version you pick up from
requirements.txt
is what will impact things. If you do want to downgrade, you should be able to fix the version in
requirements.txt
and install Python dependencies.
f

fresh-daybreak-17893

01/28/2020, 10:51 PM
What you say is consistent with what I observed on my own machine but one of my remote team members is still seeing the issue. Although I wouldn't speak for anyone else I have been led astray at times by separate versioning of
pulumi
the cli,
pulumi
the python package, and
pulumi-aws
the python package (not a criticism, I can see why the releases are managed this way). Maybe my team member is experiencing the same confusion. Thanks for the quick response.