https://serverless-stack.com/ logo
Join Slack
Powered by
I am trying to get a local start by "sst start"
# help
l
I am trying to get a local start by "sst start"
f
Hey @Loup Topalian, are you still having problem running 
sst start
?
l
yeah, it gets stuck on "Bootstraping environment"
f
hmm.. what’s ur OS, node version, yarn/npm version and SST version?
l
I'll add details tomorrow morning, but latest sst (pulled this morning) latest ubuntu, node 14 something yarn latest 1 somthing
f
Yup. When you get a chance, could you try running 
sst start
with 
--verbose
flag and send me a screenshot of your terminal. And DM me the build log in 
.build/sst-debug.log
l
ok, will definitely do that in the morning
So, the verbose shows that the toolkit is stuck in some pending operation : ``[AWS cloudformation 200 0.109s 0 retries] describeStacks({ StackName: 'CDKToolkit' })` `Stack CDKToolkit has an ongoing operation in progress and is not stable (REVIEW_IN_PROGRESS (User Initiated))``
the debug log file is empty, except for the header
f
Got it. I’m going to take a look at it.
l
maybe a stack half deployed on my aws that is making swc think we have a job in progress ?
f
From the stack status, it seems the CDKToolkit stack is stuck waiting for user to approve the deployment.
l
oh
is there a way to clean any cache etc.. ?
f
I think there is a way to not ask for user review.. let me take a quick look. I might be able to push out a quick fix for this.
In the meanwhile, I think if you went to your CloudFormation console, you can delete/cancel/approve the CDKToolkit stack to get it out of the pending state.
l
ok, i'll try that in the morning
also, one question, are you considering a more local offline mode for your SST ?
f
you mean not having to connect to real AWS resources and mocking them locally?
l
i need to try it out more, it might be great, but i must say an offline first develop mode was something pretty comfy in serverless-offline
yeah, that
or mocking a minimum of ressources
f
yeah, we saw teams ending up in the state of mocking api, sqs, sns, dynamodb, step functions… but when they start interacting with kinesis, etc they are stuck in between
at the moment we are not planning to mock services.. but we are all ears if ppl want to mock a service for a better experience
@Loup Topalian quick update on the issue. I think managed to track down the bootstrap issue. AWS CDK needs to create a CF stack in user’s account called 
CDKToolkit
. This stack creates an S3 bucket that’s similar to Serverless Framework’s S3 deployment bucket. If the stack fails to create/update, it can be stuck in the 
REVIEW_IN_PROGRESS
state, and CDK doesn’t know how to handle that. When try to bootstrap again, CDK will keep polling for the stack status waiting for the user to review the CloudFormation changeset.
I’m going to put in a fix to catch and handle this case in SST. I will try to get the fix in by the end of the week.
For now, you can just go to your CloudFormation console and remove the 
CDKToolkit
stack, and then run 
sst start
again.
Give it a try and let me know if it works for you.
l
I'll tell you once I can deploy, however i am stuck with a wrong execution policy, and can't seem to find how to pass the policy execution argument down the line to cdk
f
Oh hmm.. yeah currently SST doesn’t support that flag.
I saw ur comment int he thread.. and I’m reading up on what the flag does.
Do you know if that flag only applies to the 
cdk bootstrap
command?
l
i don't know
f
No worries.. let me poke around today..
l
you rule
f
@Loup Topalian I looked into the 
--cloudformation-execution-policies
flag. We are going to add support for this flag after we merge the removal of the forked CDK https://github.com/serverless-stack/serverless-stack/pull/82
In the meanwhile, you can run 
CDK_NEW_BOOTSTRAP=1 npx sst cdk bootstrap --cloudformation-execution-policies arn:aws:iam::aws:policy/XXXX
to manually bootstrap with the flag.
l
Great ! I was wondering exactly how I could access the cdk command thru sst. Seems like an answer. I'll check it out tomorrow at work, but kudos for taking care of that
I am doing 
sst start
with -next.15 and it seems to be deploying (the stack have being created without errors)
have a fex other problems to iron out
but the flag is working !!
f
Nice! Aight.. I think we are ready to take out the forked CDK.
2 Views
Open in Slack
PreviousNext
Powered by