v0.17.0

nightly build added @maximmi (#115)

what

• nightly docker build with tags latest and nightly

v0.16.0

geodesic version bumped, terraform 0.14 released @maximmi (#114)

what

• geodesic version bumped to 0.139.3
• terraforms install updated to rebuild with tf-14 release

why

• Minor improvements in new version
• TF 0.14 released, so rebuilding image forcing to install new one

v0.15.0

terraform-config-inspect binary moved to where it could be found by PATH @maximmi (#112)

what

• terraform-config-inspect binary moved to where it could be found by PATH

why

• to avoid issues with changed GOPATH if lookup for binary by Go module path

v0.14.0

terraform-14 added, terraform-config-inspect added @maximmi (#111)

what

• terraform 0.14 added
• terraform-config-inspect added

why

• to migrate to terraform 0.14 eventually
• to be able to run some checks for terraform code, like pinning to version

v0.13.0

Nuke IAMRolePolicy and EC2NetworkInterface associated with lambdas @osterman (#108)

what

• Nuke inline IAM policies (IAMRolePolicy)
• Nuke EC2NetworkInterface with empty tags since Lambda's do not set the tag:Name (only Description which is not available)'
• Do not nuke the zone used by atlantis us-west-2-ecs.testing.cloudposse.co

why

• Github Actions were failing their nightly executions leaving orphaned resources

v0.12.0

Add auto-release, update docker build and push @Nuru (#107)

what

• Add auto-release
• Update Docker build and push

why

• Automatically label and release when new code is available
• Tag Docker image with release label

Update Geodesic version, Terraform version and package set @Nuru (#105)

what

• Update to new Terraform packages that better support simultaneous installation
• Update Terraform 0.13 to 0.13.3
• Update to current Geodesic 0.136.1

why

• New Terraform packages use "alternatives" to better support various use cases of different versions being used in the same Docker container
• Some Terraform modules require bug fixes first available in Terraform 0.13.3.
• Keep up to date, reduce surprises due to divergeence

add terraform 0.13 support @osterman (#102)

what

• add terraform 0.13 binary

why

• so we can use it in our test-infra

Add R53 and ES configuration for aws-nuke @3h4x (#100)

what

• AWS Nuke resources:

• R53 records
• R53 Zones
• ElasticSearch

• chatops gh action file added

why

• to remove resources used in tests that were not deleted automatically

Nuke EMR, IAM Groups, EC2 Key Pairs @osterman (#99)

what

• Nuke additional resources

why

• More orphans from tests

Nuke IAM and Cloudwatch Logs @osterman (#98)

what

• Nuke IAM related resources
• Nuke Cloudwatch Logs

why

• Orphaned by EKS testing

Nuke EKS clusters @osterman (#97)

what

• Updateaws-nuke to 2.15.0-beta.1 which has support for EKS node pools
• Nuke EKS clusters

why

• Clean up orphaned clusters from tests

upgrade geodesic @osterman (#96)

what

• upgrade geodesic
• remove pinning to older versions of terraform
• remove pinning for helm/helmfile as not used right now in tests

why

all our testing is on 0.12
need go 1.13 for go modules

add golang @osterman (#95)

what

• add go package

why

• speed up builds for terratest

Update matching for aws-nuke @osterman (#93)

what

• Use proper property per resource type
• Dry-run on PRs

why

• Properties are horribly inconsistent (probably due to AWS)
• Dry-runs are critical to validate PRs

0.11.0: add aws-nuke (#92)

* add aws-nuke

* fix syntax

* Disable PR action

* Update .github/aws-nuke.yaml

Co-authored-by: Andriy Knysh <[email protected]>

Co-authored-by: Andriy Knysh <[email protected]>

0.10.0 Add `dynamodb`

what

• Add dynamodb module

why

• To provision a DynamoDB table with optional autoscaling and backup

0.9.0 Update atlantis version

what

• Update atlantis version

why

• https://github.com/cloudposse/atlantis/releases/tag/0.9.0-cp.2

0.8.0 Bump `geodesic` version. Bump `atlantis` version. Bump `terraform` version

what

• Bump geodesic version
• Bump atlantis version
• Bump terraform version

why

• Keep up to date
• Test new atlantis version with the updates from the upstream repo