https://serverless-stack.com/ logo
Join Slack
Powered by
I was setting up a new stack that references an SS...
# sst
s
I was setting up a new stack that references an SSM variable that I created manually in the AWS console. Therefore, the stack creation failed when executing 
sst start
.
Copy code
sgeoghegan-kas-api-stack | CREATE_FAILED | AWS::CloudFormation::Stack | sgeoghegan-kas-api-stack 

 ❌  sgeoghegan-kas-api-stack failed: ERROR Parameter Name /sgeoghegan/kas/api-url with a different configuration already exists.


Stack sgeoghegan-kas-db-stack
  Status: deployed

Stack sgeoghegan-kas-api-stack
  Status: failed
  Error: ERROR Parameter Name /sgeoghegan/kas/api-url with a different configuration already exists.

Failed to deploy the app
error Command failed with exit code 1.
info Visit <https://yarnpkg.com/en/docs/cli/run> for documentation about this command.
I deleted the SSM parameter manually so I could let the stack create it next time around
d
This is expected CFn behavior. You can import items into a stack, but its a little tedious.
s
Yeah, that's what I get for creating something manually while testing 🙂
However, what surprised me, is that 
sst start
ended up starting with a status of "no changes"
and it did not output the API URL as expected
d
for when I have both local and prod stacks, I wrap any SSM creations in 
if(!isLocal)
s
Copy code
===============
 Deploying app
===============

Deploying stacks

 ✅  sgeoghegan-kas-db-stack (no changes)


 ✅  sgeoghegan-kas-api-stack (no changes)


Stack sgeoghegan-kas-db-stack
  Status: no changes

Stack sgeoghegan-kas-api-stack
  Status: no changes


==========================
 Starting Live Lambda Dev
==========================

Transpiling Lambda code...
Debug session started. Listening for requests...
Rebuilding infrastructure...
No infrastructure changes detected
d
not sure on that last one, but are you "start"ing with the same "stage" as prod?
s
no, this is for local dev. The stage is my username
Copy code
AWS_PROFILE=staging AWS_SDK_LOAD_CONFIG=1 sst start --stage $(whoami)
d
and you hadnt previously deployed with whoami?
s
The process was: 1. Deploy stack via 
sst start
which failed since my stack was trying to create an SSM parameter that already existed. 2. Remove SSM parameter manually in AWS console 3. Deploy stack again via 
sst start
, which left the client running as expected. However, the stack that creates my API did not output the API URL as expected. As a result, 
sst start
is running and I have no idea what URL I should be accessing!
d
the api url is a 
CfnOutput
?
s
Yes, at the end of my stack creation
Copy code
const api = new sst.Api(this, "api", {...})  

  // Show the endpoint in the output
    this.addOutputs({
      ApiEndpoint: api.url
    });
I can see that the API was created in the AWS console, where I can grab the URL
d
ive never ran into that issue, sounds like some kind of CDK blip.
s
yeah, it's not a blocker or anything, just unexpected behavior
well, unexpected by me at least 🙂
I gotta buy that new CDK book
d
I gotta buy that new CDK book
@Seth Geoghegan, which?
s
It's not out yet, but I've seen it referenced around Twitter lately: https://thecdkbook.com/
f
@Derek Kershner thanks for chiming in!
@Seth Geoghegan what version of sst r u on? Can you try updating it to the latest and give it a shot?
There was a recent fix for 
sst start
not deploying the latest changes.
s
I'm on 
0.50.1
f
I see.. think I know what’s going on… lemme take a look
Open in Slack
PreviousNext
Powered by