sparse-intern-71089
07/25/2022, 3:12 AMlittle-cartoon-10569
07/25/2022, 3:25 AMlittle-cartoon-10569
07/25/2022, 3:26 AMsquare-ability-48831
07/25/2022, 4:33 AMpulumi:providers:aws
- even with access to the old intel stack and installing all the latest pulumi versions, the stack is still pinned to use 3_30_1
instead of latest 5_10_0
.billowy-army-68599
docker run --entrypoint bash --rm -it --platform linux/amd64 pulumi/pulumi
Then update the provider version in the stack
npm update @pulumi/aws
You’ll need to run a successful deploy with the old and new version to update the provider version
pulumi up
From then on, you can go back to your machinebillowy-army-68599
just not sure how to upgrade a dev env/stack to use a newer pulumiprovidersaws - even with access to the old intel stack and installing all the latest pulumi versions, the stack is still pinned to use 3_30_1 instead of latest 5_10_0Provider versions are pinned inside the state. We know this is painful, and have https://github.com/pulumi/pulumi/issues/9878 open to make it easier
square-ability-48831
07/25/2022, 6:16 AMgreat-sunset-355
07/25/2022, 7:30 AMgreat-sunset-355
07/25/2022, 7:31 AMpulumi up --target 'urn:pulumi:STACK::iam::pulumi:providers:aws::MyNewProvider'
little-cartoon-10569
07/25/2022, 7:50 AMsalmon-account-74572
07/25/2022, 2:54 PMbillowy-army-68599