Releases: gruntwork-io/terraform-aws-couchbase
v0.6.1
v0.6.0
Modules affected
couchbase-cluster
couchbase-iam-policies
couchbase-server-security-group-rules
load-balancer-target-group
load-balancer
sync-gateway-security-group-rules
Description
- Terraform 0.15 upgrade: We have verified that this repo is compatible with Terraform
0.15.x
!- From this release onward, we will only be running tests with Terraform
0.15.x
against this repo, so we recommend updating to0.15.x
soon! - To give you more time to upgrade, for the time being, all modules will still support Terraform
0.12.26
and above, as that version has several features in it (required_providers
withsource
URLs) that make it more forwards compatible with0.15.x
. - Once all Gruntwork repos have been upgrade to work with
0.15.x
, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
- From this release onward, we will only be running tests with Terraform
Related links
v0.5.0
Modules affected
couchbase-cluster
couchbase-iam-policies
couchbase-server-security-group-rules
load-balancer-target-group
load-balancer
sync-gateway-security-group-rules
Description
- Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform
0.14.x
!- From this release onward, we will only be running tests with Terraform
0.14.x
against this repo, so we recommend updating to0.14.x
soon! - To give you more time to upgrade, for the time being, all modules will still support Terraform
0.12.26
and above, as that version has several features in it (required_providers
withsource
URLs) that make it more forwards compatible with0.14.x
. - Once all Gruntwork repos have been upgrade to work with
0.14.x
, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
- From this release onward, we will only be running tests with Terraform
Related links
v0.4.0
Modules affected
couchbase-cluster
couchbase-iam-policies
couchbase-server-security-group-rules
load-balancer-target-group
load-balancer
sync-gateway-security-group-rules
Description
- Terraform 0.13 upgrade: We have verified that this repo is compatible with Terraform
0.13.x
!- From this release onward, we will only be running tests with Terraform
0.13.x
against this repo, so we recommend updating to0.13.x
soon! - To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (
required_providers
withsource
URLs) that make it more forwards compatible with0.13.x
. - Once all Gruntwork repos have been upgrade to work with
0.13.x
, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.
- From this release onward, we will only be running tests with Terraform
Related links
v0.3.0
Modules affected
install-couchbase-server
[BACKWARDS INCOMPATIBLE CHANGES]install-sync-gateway
[BACKWARDS INCOMPATIBLE CHANGES]run-couchbase-server
[BACKWARDS INCOMPATIBLE CHANGES]couchbase-cluster
load-balancer-target-group
Description
-
Updated this repo to the latest Couchbase versions:
install-couchbase-server
now installs Couchbase Enterprise6.6.0
and Couchbase Community6.5.1
by default.- We now use the CentOS 7 (instead of CentOS 6) versions of the Couchbase installers for Amazon Linux.
- We now install
bzip2
as part of the install process, as the Couchbase installers rely on it, and not all Linux distros have it installed by default. run-couchbase-server
uses--username
and--password
params with the Couchbase CLI instead of--user
and--password
.run-couchbase-server
now prependshttp://
to node URLs that don't already have a prefix when calling theserver-add
command (otherwise, Couchbase assumes those URLs use TLS).
-
Updated this repo to the latest Sync Gateway Versions:
install-sync-gateway
now installs Sync Gateway Enterprise and Sync Gateway Community2.7.3
.
-
Updated this repo to work with AWS Provider 3.x:
- The
couchbase-cluster
module now sets theignore_changes
lifecycle setting onload_balancers
andtarget_group_arns
attributes. As of AWS Provider 3.x, if you useaws_autoscaling_attachment
, you MUST haveignore_changes
set on these attributes, or your load balancer will be removed (see corresponding issue in the AWS provider). Since thecouchbase-cluster
module doesn't let you use these attributes anyway, this should be a backwards compatible change that allows this module to work properly with a load balancer. - The
load-balancer-target-group
has been updated to use the new syntax for theaws_alb_listener_rule
resource. In addition to thepath-pattern
rules you could pass in viarouting_condition
, you can now also pass inhost-header
,http-request-method
, andsource-ip
rules.
- The
Migration guide
- We only recommend upgrading to this release if you're also ready to upgrade to Couchbase 6.x and Sync Gateway 2.x. We are no longer testing this repo with older versions (e.g., Couchbase 5.x).
- We recommend building a new AMI for Couchbase and Sync Gateway and deploying them with the new versions of the Terraform modules.
- If you're using the
run_couchbase_cli_with_retry
function (e.g., in your User Data scripts), we recommend updating theexpected_message
parameter (second argument) to"SUCCESS:"
. The CLI used to output values such as"SUCCESS: RBAC user set"
, but most of these have changed, so it's more reliable to look solely for"SUCCESS:"
now.
Related links
v0.2.4
v0.2.3
v0.2.2
v0.2.1
Modules affected
couchbase-cluster
Description
- You can now configure the IAM role path and permissions boundary in the
couchbase-cluster
module using the new input variablesinstance_role_path
andinstance_permissions_boundary
, respectively.
Special thanks
- Thank you to @dgrizzanti for the PR!
Related links
v0.2.0
Modules affected
couchbase-cluster
[BREAKING CHANGES]couchbase-iam-policies
[BREAKING CHANGES]couchbase-server-security-group-rules
[BREAKING CHANGES]load-balancer-target-group
[BREAKING CHANGES]load-balancer
[BREAKING CHANGES]sync-gateway-security-group-rules
[BREAKING CHANGES]
Description
All the modules are now terraform 0.12.0 compatible. Note that this means the modules are no longer compatible with terraform 0.11 and under. Starting this release, you must use terraform 0.12.0 or greater to use this module.
All the module variables have been updated to use concrete types based on the new type system introduced in terraform 0.12.0. You can learn more about the types in the official documentation.
Note that as part of this, we switched to using null
to indicate unset values when passing them through to resources. If you were previously using a 0 value (""
for strings and 0
for numbers), review the module variables.tf
file to double check if the 0 value has been converted to a null
.