What’s the preferred way to run a script after a deploy? We need to register the (generated) URLs as webhooks with some external API

If you want to keep it all within AWS you can create a custom resource. That's effectively a lambda that runs as part of your deploy

seems like a very common use-case to me 😛 maybe something to include in SST?

It's not too crazy but probably can create a more convenient wrapper around custom resources. It's still a new pattern for me and I'm still evaluating if I like the approach

Thanks I’ll take a look 🙏

I think running scripts is a pretty common use case. There’s an open issue for adding db migration support (https://github.com/serverless-stack/serverless-stack/issues/483). But I wonder if just adding support for running any type of scripts would be more helpful. @Frank knows more about this.

@Danny Just curious, why not have a script in ur local, and run it after deploy? ie.

package.json

"scripts": {
  "deploy": "sst deploy && ./my-local-script"
}

ah I wasn’t sure deploy is ran like that

Ah that was more like if you wanted to run something locally. When deployed through SEED, you can run the script in the

after_deploy

hook in your buildspec https://seed.run/docs/adding-a-build-spec#seedyml Alternatively, you can run it in the Post-Deploy Phase https://seed.run/docs/adding-a-post-deploy-phase.html

yes we have that and it’s slow

Yup, let me talk to the team tmr, that’s something we are looking to add very soon.

in this case it only has to run when the API gateway URL is known (first deploy) or if it changes