[Possible v0.59.1 bug]: I think this bug may relate to changing the name of the stack.

console.log({ stackName })
  // eg. idx-dvb-idx
  new MyStack(app, serviceName, {
    stackName,
  })

which results in the debug and main stacks to deploy without error (see photos)… however running

yarn start --stage dvb-idx

ends up failing in the command line with

dvb-idx-idx-idx failed: The dvb-idx-idx-idx stack contains no resources.

Which looks like one too many “idx”??

Taking a look..

removing that

stackName

from StackProps fixes the issue. So must me something in the code that ignores that now.

What was the

serviceName

and

stackName

set to? ^ trying to reproduce the issue on my end I’m able to reproduce it.. looking into ti

well… I think SST does

[stage]-[sst.json-name]-[sst.Stack.name]

and for now… we only ever have a single stack…. so we do….

[package.json-name]-[stage]

serviceName is just a script that pulls the package.json > name.

Got it. Yeah I managed to tracked down the issue, related to a change CDK made in v2. Working on a fix.

thanks Frank! will do…. just need to fix another issue first.