v0.25.0

Keep IAM Users and Organization Role @goruha (#125)

what

• Keep IAM Users and Organization Role

why

• AWS Nuke use IAM user so we need to have it until we cleanup all other resources
• Organization role required to access account from root account

references

• DEV-389 deprecate-old-testing-org-and-iam-keys

v0.24.0

Cleanup all resources @goruha (#124)

what

• Cleanup all resources

why

• Prepare to drop testing.cloudposse.co

References

• DEV-389 Deprecate old testing org and IAM keys

v0.23.0

Auto release fix @goruha (#123)

What

• Use auto relesase shared workflow

Why

• https://cloudposse.atlassian.net/browse/DEV-1747

v0.22.0

Add additional resources to aws-nuke @dylanbannon (#121)

what and why

• Add additional resources to aws-nuke. Found abandoned
  • NeptuneCluster & snapshots
  • RDSDBCluster & shapshots
  • SNSTopic
  • KMS Keys and aliases
  • EC2 Launch Templates
  • SSMParameters
  • CodeDeployApplications
  • CloudWatchAlarms
  • MQ Brokers
• Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

v0.21.0

aws-nuke update @Nuru (#120)

what

• Update aws-nuke 2.15.0 -> current 2.17.0
• Add resources to nuke:
  • IAMInstanceProfile
  • IAMInstanceProfileRole
  • MSKCluster
  • MSKConfiguration
• Alphabetize bulk of list of resources to nuke

why

• Support for additional resources
• Needed to properly clean up MSK and ElasticBeanstalk
• Make resources easier to find in config file

notes

• Automated nightly aws-nuke was failing since Dec 22, 2021 due to lack of support for AWS MWAA and failure to clean up MSK and ElasticBeanstalk.
• Still waiting for MWAA support. See rebuy-de/aws-nuke#745

v0.20.0

Add Spotinst integration @Nuru (#113)

what

• Add Spotinst integration
• terraform fmt

why

• Support testing of Spotinst components
• Keep things standardized

v0.19.2

Allow manual kickoff of aws-nuke @Nuru (#119)

what

• Allow manual kickoff of aws-nuke to delete resources
• Change scheduled nuke time to noon UTC, which is 4am PST and 5am PDT

why

• Previous PR only allowed manual kickoff to see if resources needed to be deleted
• Previous scheduled nuke was during workday in US Pacific time zone, meaning a greater chance of nuking a test underway

v0.19.1

Update aws-nuke workflow @Nuru (#118)

what

• [aws-nuke workflow] update from obsolete AWS_SECRET_KEY to current AWS_SECRET_ACCESS_KEY
• [aws-nuke workflow] update checkout action to v2
• [aws-nuke workflow] add workflow dispatch for dry run

why

• Some tools no longer work with AWS_SECRET_KEY as it has been deprecated for a long time
• Security improvements
• Enable status check of current environment

v0.19.0

Tune aws-nuke: skip S3Objects, include RedShift @Nuru (#117)

what

• Tune aws-nuke: skip S3Objects, delete RedShift resources, ECS Task Definitions, and OIDC connectors
• Update Geodesic to current and install Terraform 0.15 and 1.x
• Disable nightly Docker builds

why

• Action was timing out after 6 hours, probably because of the overhead of deleting S3 objects one at a time. Not necessary to delete S3 Objects because we will delete entire S3 Buckets which will cause S3 Objects to be deleted as well.
• We now have a tests that provision RedShift clusters and OIDC connectors, but we were not deleting them.
• Support current Terraform version as well as legacy version.
• Image is stable, does not change with nightly builds, and testing now uses curl to pull latest configuration anyway.

v0.18.0

Update Geodesic, restore some old support @Nuru (#116)

what

• Update Geodesic to 0.141.1
• Restore AWS_VAULT default support
• Restore support for Makefile-based Terraform
• Restore default direnv enabled

why

• This repo still uses these features, but they were phased out as defaults in Geodesic 0.138.0