- Updated dependencies
- Updated
package.json
engines.node
property to reflect changes from v4
- Updated dependencies
- Fixed error destroying an app that did not deploy correctly the first time
- Transitioned from
aws-sdk
toaws-lite
- Added Node.js 20.x to test matrix
- Breaking change: removed support for Node.js 14.x (now EOL, and no longer available to created in AWS Lambda)
- Updated dependencies
- Updated dependencies
- Updated dependencies
- Added Node.js 18.x to test matrix
- Updated dependencies
- Updated dependencies
- Deleting a named stack no longer deletes staging environment SSM params
- Updated dependencies
- Fixed issue where destroying an environment with >9 env vars would fail; fixes #1351, thanks @pgte!
- Updated dependencies; sub-dep
lambda-runtimes
addsnodejs16.x
.
- Updated dependencies
- Fix error reporting when run from
arc
(and not as standalone)
- Breaking change: bare CLI arguments (e.g.
destroy force
) as aliases to flags are no longer used - Stop publishing to the GitHub Package registry
- Updated dependencies
- Updated dependencies
- Updated dependencies
- 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
- Updated dependencies
- Added a
--no-timeout
flag, which causesdestroy
to wait until the CloudFormation Stack is deleted before exiting
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)
- 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 thedestroy
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
- Fixed failing destroy operations when CloudFormation Stack was already deleted; this fixes #1155
- Detection of resources that require use of the
--force
flag is now done sooner, so as to fail faster in the case the flag is needed
- Use of latest architect inventory for plugins support.
- Fixed failing destroy operations when app doesn't have any SSM parameters (which is unusual, but possible in certain circumstances)
- Added support for custom stage names (aka stack names), fixes #1055; thanks @filmaj + @ryanbethel!
- Added
--now
CLI flag in case you just like really need to destroy stuff right. now.
- Specifying the app to destroy, formerly the
--name
CLI flag, should now be used as--app
--app
and--name
can now be used together
- Made S3 bucket removal idempotent: if buckets do not exist when attempting to clear/remove them, don't throw an exception.
destroy
now wipes out any CloudWatch logs, SSM Parameters added byarc env
(for the specific environment being destroyed) and wipes and deletes the deployment bucket used during CloudFormation deploys.
- Emptying out S3 bucket contents now supports buckets that contain more than 1,000 objects.
- Updated dependencies
- Implemented Inventory (
@architect/inventory
) - Updated dependencies
- Say hello to
@architect/destroy
! - Fixed src/cli to export a function
- Fixed src/cli to only show banner if being run standalone
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.