I have a few stacks which currently are deploying ...
# sst
j
I have a few stacks which currently are deploying to
us-east-1
because of the
region
property inside
sst.json
. If I wanted to move all of them to
us-east-2
is there anything I need to do except change that property and deploy?
t
that would work but make sure you sst remove the first set before switching
Or can go into cfn console and delete the stacks manually
j
@thdxr
Copy code
I'm seeing `ERROR: Failed to run: CDK_DISABLE_VERSION_CHECK=true CDK_NEW_BOOTSTRAP=true cdk bootstrap --app .build/cdk.out --no-color --verbose
during build. any idea why?
t
This is for
sst build
?
can you try deleting the
.sst
folder
j
i haven't been using any cli commands, just pushing to seed.run and it autodeploys
t
ah hm might need @Frank to take a look
j
cool thanks for pinging him! the one thing it might be is that I have a hostedZone inside cdk.context.json which is in us-east-1, and sst.json now has us-east-2. but i don't see anything specific in the build logs that says thats the error
f
Hey @Jason, are you still having this issue?
Can you send me the link to the failed build?
j
Yes, will send links via dm
f
@Jason I looked at the build log u sent over, it seems the CDK bootstrap stack in ur account (46xxxxxxxx64) us-east-2 region is stuck in the
ROLLBACK_COMPLETE
state. And it needs to be manually removed.
If you can go into that account > go into CloudFormation console > select us-east-2 region > look for the stack named
CDKToolkit
> remove the stack.
Then try deploying again.
Let me know how it goes.
j
Ah I tried that at the time, and it just had the same issue. But i'll try again on Monday and report back to be sure
f
Yup let me know if still no luck.
j
Sorry it's taken a while to get back to this. Finally tried again and ran into the same issue
Definitely did not have a CDKToolkit stack at the time of building
Though I have one now in the "ROLLBACK_COMPLETE" state since the build has failed
f
@Jason can u try removing the
cdk-hnb659fds-assets-xxxxxxxxxx-us-east-2
bucket from ur AWS S3 console and give it a try again?
j
Awesome, it builds successfully after that
Thanks for the help @Frank!