Does SST or CDK-pros have any guidance on potentials around “post deploy” hooks for scripting additional

aws-sdk

work against resources? One limitation with CDK/Cloudform in my experience is the

sync

(vs.

async

) nature of it all - it’s the key reason I do love terraform, ability to interrogate deployed resources and use APIs to modify them (outside of the creation). Specifically, I’m looking at some additional SNS Topic properties, which led me to https://stackoverflow.com/a/65703536 (and I’ve verified cloudform still does not support modifying these properties).

Yeah Terraform is a lot cleaner in so many ways

riiiight, yeah

I never actually looked into what's in there but that makes sense

@thdxr can you point me into direction/location where SST does this? wouldn’t mind ape-ing ya’lls pattern there

SST internals usually aren't usually great examples of best practices because we choose to absorb a lot of complexity if it makes it easier for the user. So sometimes we do ugly things because it makes things less ugly for the user

which we do appreciate lol

These docs have some basic examples: https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-cloudformation.CustomResource.html

cool, yeah - I can follow along there

Be careful with them as if they error your stack gets in a weird place and is annoying to delete

good advice, thanks 👌

Sorry linked you to the wrong one: https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_core.CustomResource.html

✔️ thanks

just a small fyi here - we did a smile bash script for our project - to be able to do some black magic after the deployment - we use it when working locally as well as CI (Github Actions) - I know it adds yet another layer - but still - it was simple to do and does the trick