https://serverless-stack.com/ logo
Join Slack
Powered by
Hey all! We had to specify the naming "Qualifier" ...
# help
p
Hey all! We had to specify the naming "Qualifier" for the bootstrapping stack (CDKToolKit) due to restrictions on AWS resource-naming imposed by our IT dept, which is fine for normal deployment if we override the 
DefaultStackSynthesizer
. However, when we try to deploy a debug stack for local debugging with 
sst start
, it gets caught in a failing loop in which it keeps trying to create a new bootstrapping stack, which fails because the default resource names violate our restrictions. How can we force sst/cdk to use our already-existing bootstrapping stack?
f
thinking… 🤔
Hey @Philipp Gaissert, just to clarify, did you bootstrap manually using 
cdk bootstrap --qualifier xxxxxx
?
p
yep!
f
And currently are you passing in the qualifier when you create Stacks in ur SST app?
Copy code
new MyStack(app, "my-stack", {
  synthesizer: new cdk.DefaultStackSynthesizer({
    qualifier: 'xxxxxx',
  }),
});
like this?
p
exactly
f
Let me talk to the team about this. Will keep you posted.
Hey @Philipp Gaissert, you can now customize the synthesizer for the Debug Stack in v0.65.3
Copy code
export function debugApp(app) {
  new sst.DebugStack(app, "debug-stack", {
    synthesizer: new cdk.DefaultStackSynthesizer({
      qualifier: 'randchars1234',
    }),
  });
}
This goes into your 
stacks/index.js
Let me know if you have any questions.
p
We were able to get this working! Thank you so much, @Frank !
f
Awesome!
p
For clarification, it's fine putting this in the same index.ts file as 
export default function main(app: <http://sst.App|sst.App>): void {...}
?
f
yup, the 
debugApp()
callback have to go into 
index.ts
8 Views
Open in Slack
PreviousNext
Powered by