It seems like Router invalidations are only handled at the moment by the individual Ssr/StaticSite components. However, we have a router pointing to another router and other external urls and need to control the invalidation separately. The docs mention an invalidation option, but when experimenting with it, it doesn't seem to be wired up.
Since our invalidations are always tied to our own deploys, our use case would be satisfied with the documented API:
new sst.aws.Router("...", {
// ...
invalidation: {
wait: false,
paths: ["/*"],
token: "our-own-computed-key",
},
});
Or allowing to create the internal sst.aws.DistributionInvalidation as a public component.
It seems like Router invalidations are only handled at the moment by the individual Ssr/StaticSite components. However, we have a router pointing to another router and other external urls and need to control the invalidation separately. The docs mention an
invalidationoption, but when experimenting with it, it doesn't seem to be wired up.Since our invalidations are always tied to our own deploys, our use case would be satisfied with the documented API:
Or allowing to create the internal
sst.aws.DistributionInvalidationas a public component.