Hi all looking for any guidance if anyone s encountered need Pulumi Community #general

Hi all, looking for any guidance if anyone's encou...

square-ability-48831

07/25/2022, 3:12 AM

Hi all, looking for any guidance if anyone's encountered needing an old

pulumi resource aws

version - but i can't install v3.30.1 since I'm on a new M1 mac, trying to take over a 1 year old deployment built with intel. is it possible to upgrade it to latest (~5.10.0) and still use the same state file on pulumi.com? I'm trying to avoid needing to manually import everything already deployed. is it possible to get the old stacks updated to the latest aws provider?

little-cartoon-10569

07/25/2022, 3:25 AM

In theory, you could export the old stack, update the dependencies, and import it. But the risk of being affected by an incompatible API is very high given how far apart the versions are, so I wouldn't do this.

little-cartoon-10569

07/25/2022, 3:26 AM

Just use a different computer. Maybe you could fire up a short-lived EC2 instance or similar in order to use the current code? Then once you've upped with updated dependencies, you can start working from your Mac.

square-ability-48831

07/25/2022, 4:33 AM

"just use another computer" yeah is great but what a pain, i don't want to have a trail of different computers/ec2/images for old deploys. is there no way to bring a stack onto a newer aws provider? just not sure how to upgrade a dev env/stack to use a newer

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

07/25/2022, 4:46 AM

@square-ability-48831 you can start a docker container with the right arch:

Copy code

docker run --entrypoint bash --rm -it --platform linux/amd64 pulumi/pulumi

Then update the provider version in the stack

Copy code

npm update @pulumi/aws

You’ll need to run a successful deploy with the old and new version to update the provider version

Copy code

pulumi up

From then on, you can go back to your machine

billowy-army-68599

07/25/2022, 4:48 AM

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_0

Provider 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 AM

thanks for the insight, guess i'll just go through the pain of destroying and recreating, glad i have the luxury for this project!

great-sunset-355

07/25/2022, 7:30 AM

you can update aws provider without create/destroy

great-sunset-355

07/25/2022, 7:31 AM

pulumi up --target 'urn:pulumi:STACK::iam::pulumi:providers:aws::MyNewProvider'

little-cartoon-10569

07/25/2022, 7:50 AM

Wouldn't that require the current binaries to run? But they don't, because they're not built for the M1. At least, I thought that was the problem...

salmon-account-74572

07/25/2022, 2:54 PM

I would think you’d be able to use the older Intel binaries on the M1 (via Rosetta). Not the same, but I was accidentally running the Intel version of Go on my M1 for several months before I realized. 🤦🏻

billowy-army-68599

07/25/2022, 2:55 PM

I also made this mistake 😂

Open in Slack

Previous Next