Change SST logicalPrefixedName naming to match serverless 3.0 update about sst

[jayair]

Yeah their naming used to be a bit all over the place before. This is a bit of a bigger change for sst since it affects existing apps. But we are trying to figure out if there is a way to migrate some services over from Serverless Framework and this naming scheme is a part of that.

[jayair]

Hmm the logicalPrefixedName wasn't meant to be in sync with Serverless. It was more meant to ensure uniqueness when deployed to different stages.

What's your use case for keeping them in sync?

[brucek]

oh really? as a new serverless user, I am following https://serverless-stack.com/chapters/building-a-cdk-app-with-sst.html to get started

With the serverless 3.0 update, I now have a bunch of AWS infrastructure stacks named ${stage}-${service} while my main serverless stack is called ${service}-${stage}. It seems like a better situation to have all the stacks listed together in the AWS CloudFormation console, and it seemed like Serverless would be the logical lead on naming, and/or that the same logic for making that change would apply here.

[brucek]

Here is the source issue in Serverless and their rationale (seems like the same logic: keep them listed together in AWS console): serverless/serverless#2918

[thdxr]

Going to close this issue for now, @brucek let us know if this is still a problem for you and we can re-open it