Skip to content

Releases: exasol/terraform-aws-exasol

2.0.0: Update CloudFormation template and new DB version

30 Sep 05:30
19330f2
Compare
Choose a tag to compare

Summary

This release updates the NodeJS version for Lambdas used by the CloudFormation template during deployment to 20.x.

Breaking Change

The "Bring your Own License" (BYOL) AMI images are deprecated and not available any more. Specifying your own license file is not possible any more. Please use the "Pay as you go" (PAYG) AMI images, e.g. Exasol-R7.1.26-PAYG.

Bug Fixes

  • #39: Fixed nodejs version in CF template

1.0.4: Fix deployment

11 Mar 08:21
85f7718
Compare
Choose a tag to compare

Summary

This release updates the NodeJS version for Lambdas used by the CloudFormation template during deployment to 16.x.

Starting with this version terraform-aws-exasol is tested with Terraform 1.5.7. We recommend using the same version.

Bug Fixes

  • #37: Fixed nodejs version in CF template

1.0.3: Fix deployment

27 Jun 09:03
303e4c9
Compare
Choose a tag to compare

Summary

This release updates the NodeJS version for Lambdas used by the CloudFormation template during deployment.

Starting with this version terraform-aws-exasol is tested with Terraform 1.5.1. We recommend using the same version.

Bug Fixes

  • #29: Added name to workflow files with matrix builds
  • #32: Fixed nodejs version in CF template

Migrated to Github Actions

24 Nov 07:49
bb2806f
Compare
Choose a tag to compare

Summary

In this release, we migrated our Continuous Integration (CI) from Travis CI to Github Actions.

Refactoring

  • #27: Migrated to Github Actions from Travis CI

Security fix

10 Jun 13:14
6453d7b
Compare
Choose a tag to compare

Summary

In this release we fixed a security issue. By an unquoted password it was
possible to execute code on the host running terraform.

Refactoring

  • #23: Added integration test

Bugfixes

  • #21: Fixed unescaped password

Fixed instance tags and outputs

08 Dec 10:22
bc97b4e
Compare
Choose a tag to compare

Bugfixes

  • #13: The setup assigned wrong tags to ec2 instances
  • #18: Fixed the outputs