Which package(s) are affected?
@aws-blocks/pipeline / deploy CLI
Describe the bug
npm run deploy produces 0-byte stdout during the CloudFormation phase. When run in the background the process is SIGTERM'd (exit 143) even though the underlying CloudFormation deploy succeeds independently. There is no reliable progress signal, so callers must poll describe-stacks by hand and cannot tell success from failure.
Evidence
observed across all 3 reps of document-ingestion-pipeline (preamp batch manual-deploy-20260717-103949-1339). Consumers re-ran deploys chasing phantom failures, driving 2-3x cost (~$15/run vs $5-8) and the longest runtime (~22min) of any framework on the task.
Expected
Deploy streams progress to stdout and returns a clear terminal status; a deploy that is still running is not SIGTERM'd.
Suggested fix
Stream CloudFormation progress events to stdout and decouple the CLI lifecycle from the in-flight deploy
Which package(s) are affected?
@aws-blocks/pipeline / deploy CLI
Describe the bug
npm run deployproduces 0-byte stdout during the CloudFormation phase. When run in the background the process is SIGTERM'd (exit 143) even though the underlying CloudFormation deploy succeeds independently. There is no reliable progress signal, so callers must polldescribe-stacksby hand and cannot tell success from failure.Evidence
observed across all 3 reps of document-ingestion-pipeline (preamp batch manual-deploy-20260717-103949-1339). Consumers re-ran deploys chasing phantom failures, driving 2-3x cost (~$15/run vs $5-8) and the longest runtime (~22min) of any framework on the task.
Expected
Deploy streams progress to stdout and returns a clear terminal status; a deploy that is still running is not SIGTERM'd.
Suggested fix
Stream CloudFormation progress events to stdout and decouple the CLI lifecycle from the in-flight deploy