Hey guys, quick question;
How have you guys handl...
# helps
Stephen McGowan
01/07/2022, 11:10 AMHey guys, quick question;
How have you guys handled working with SST within a team, specifically, using DynamoDb tables or S3 buckets in your stack.
We have set up .sst to have a stage prefix, but this only seems to apply to lambdas, queues, sns etc and not buckets or tables. Am I missing something or is there a best practice approach to this? Thanks 🙂
o
Omi Chowdhury
01/07/2022, 11:35 AMYup, include the stage name in your dynamo table name and s3 bucket name, then import them as env variables into your lambda functions (or wherever they get used)
s
Stephen McGowan
01/07/2022, 11:46 AMThanks for the response! So do you not include a stage in .sst stage file?
o
Omi Chowdhury
01/07/2022, 11:48 AMWe do - that appears in app.stage inside SST, then the table name includes app.stage
Omi Chowdhury
01/07/2022, 11:50 AMHere’s what we do for a utility queue, same idea would work for any resource:
Copy code
import { Duration } from '@aws-cdk/core';
import { App, Queue, Stack } from '@serverless-stack/resources';
import { StackProps } from 'sst-resources/types';
export default class SinkQueueStack extends Stack {
constructor(app: App, id: string, props: StackProps) {
super(app, id, props);
new Queue(this, `${id}-${app.stage}`, {
sqsQueue: {
retentionPeriod: Duration.seconds(60), // 60s is the min
},
});
}
}s
Stephen McGowan
01/07/2022, 11:52 AMOh that's nice, thanks for that much appreciated @Omi Chowdhury 👏
t
thdxr
01/07/2022, 2:07 PMHm why do you need to do this?
thdxr
01/07/2022, 2:07 PMIs it because you want the resource name itself to follow a format?