@architect/destroy - npm Package Versions

[2.0.3] 2021-11-16

Changed

• Updated dependencies

[2.0.2] 2021-10-12

Changed

• Updated dependencies

[2.0.0 - 2.0.1] 2021-07-22

Changed

• Breaking change: removed support for Node.js 10.x (now EOL, and no longer available to created in AWS Lambda) and Node.js 12.x
• Breaking change: the --name flag can no longer be used in place of --app to destroy apps; --app must now be used to destroy apps, while --name may only be used to destroy stacks; fixes #1165
• Updated dependencies

[2.0.0 - 2.0.1] 2021-07-22

Changed

• Breaking change: removed support for Node.js 10.x (now EOL, and no longer available to created in AWS Lambda) and Node.js 12.x
• Breaking change: the --name flag can no longer be used in place of --app to destroy apps; --app must now be used to destroy apps, while --name may only be used to destroy stacks; fixes #1165
• Updated dependencies

[1.3.0] 2021-06-22

Added

• Added a --no-timeout flag, which causes destroy to wait until the CloudFormation Stack is deleted before exiting

Changed

• destroy now pings the CloudFormation API to check for Stack deletion every 10 seconds (instead of increasingly backing off starting from 10 seconds to 60 seconds)

[1.2.5 - 1.2.6] 2021-06-21

Changed

• Updated dependencies

[1.2.5 - 1.2.6] 2021-06-21

Changed

• Updated dependencies

[1.2.4] 2021-06-09

Changed

• If the CloudFormation DeleteStack operation detects that the Stack has a status of DELETE_FAILED, it will now report this, along with the status reason, and exit with a non-zero code rather than wait for the destroy command timeout to run out; this fixes #1156
• destroy will now exit with a non-zero code if any errors are raised during its execution