Releases: cloudposse/terraform-aws-lambda-elasticsearch-cleanup
Releases · cloudposse/terraform-aws-lambda-elasticsearch-cleanup
0.7.0: build lambda (#19)
* build lambda * upload with public readability; * test download * fix action
0.6.0 Update `terraform-external-module-artifact` version
what
- Update
terraform-external-module-artifactversion
why
- Add
enabledvariable to the module - When the
terraform-external-module-artifactmodule is used in this module withenabledvariable set tofalse,terraform-external-module-artifactneeds to be disabled as well (otherwise it throws errors that it can't download the artifact)
references
0.5.0 Convert to TF 0.12. Add tests. Add Codefresh test pipeline. Add `slash-command-dispatch` GitHub Actions workflow
what
- Port module to Terraform 0.12
- Pin all providers
- Add example for testing
- Add
batsandterratestfor the example - Add Codefresh badge to point to the test pipeline in
terraform-modulesproject - Update README
- Add
slash-command-dispatchGitHub Actions workflow
why
- Module currently does not work with 0.12. Much easier syntax
- Better regression control
- Automatically test the example on every commit and pull request
- Provision resources on AWS in the test account and check the outputs for the correct values
terraform-modulesproject contains pipelines for all terraform modulesslash-command-dispatchGitHub Actions workflow: In a repo with the GitHub actions workflow present, when a PR is opened, we can comment on the PR with commands/build-readmeand/terraform-fmtto rebuild README and format terraform code and push the changes back to the PR repo
0.4.2
0.4.1 Fix index cleanup lambda failure due to AWS changes
0.4.0 Fix SNS
0.3.0: Use relative path name for lambda
Incompatible change (#8):
Previously we used the full path name for the lambda file. We now use the path name relative to the current working directory. This change will reduce unnecessary Terraform updates in the future, but will cause one when first applied.