Is there a fool-proof way to

cat

out the current syth’d template before deploy / as part of deploy? Just realizing that as part of our pipeline… when a build errors out…. we really have no way to see what “template” it was trying to deploy, since CFN usually has already rolled back by the time we come in to investigate the issue.

sst build

? per https://docs.serverless-stack.com/packages/cli#build

Thanks @Adam Fanello, but wouldn’t that cost x2 build cycles (time) since the deploy builds as well? I think what I’m after is maybe an option for the deploy command to console out the template or perhaps allow for hooks into the deploy steps that allow for us to run a command at that point in the process.

Ah. You could have that generate the packages and then deploy the CloudFormation templates in the pure AWS ways, but that'd sure be a hassle. Your question sounded like you wanted to see the template as a means of debugging. I didn't realize you wanted to do it that way every time.

Yeah.. we haven’t been able to prioritize this.. being able to deploy from

sst build

output without rebuilding should help https://github.com/serverless-stack/serverless-stack/issues/779