Releases: gruntwork-io/terraform-aws-couchbase
v0.6.1
v0.6.0
Modules affected
couchbase-clustercouchbase-iam-policiescouchbase-server-security-group-rulesload-balancer-target-groupload-balancersync-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.xagainst this repo, so we recommend updating to0.15.xsoon! - To give you more time to upgrade, for the time being, all modules will still support Terraform
0.12.26and above, as that version has several features in it (required_providerswithsourceURLs) 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-clustercouchbase-iam-policiescouchbase-server-security-group-rulesload-balancer-target-groupload-balancersync-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.xagainst this repo, so we recommend updating to0.14.xsoon! - To give you more time to upgrade, for the time being, all modules will still support Terraform
0.12.26and above, as that version has several features in it (required_providerswithsourceURLs) 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-clustercouchbase-iam-policiescouchbase-server-security-group-rulesload-balancer-target-groupload-balancersync-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.xagainst this repo, so we recommend updating to0.13.xsoon! - 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_providerswithsourceURLs) 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-clusterload-balancer-target-group
Description
-
Updated this repo to the latest Couchbase versions:
install-couchbase-servernow installs Couchbase Enterprise6.6.0and Couchbase Community6.5.1by default.- We now use the CentOS 7 (instead of CentOS 6) versions of the Couchbase installers for Amazon Linux.
- We now install
bzip2as part of the install process, as the Couchbase installers rely on it, and not all Linux distros have it installed by default. run-couchbase-serveruses--usernameand--passwordparams with the Couchbase CLI instead of--userand--password.run-couchbase-servernow prependshttp://to node URLs that don't already have a prefix when calling theserver-addcommand (otherwise, Couchbase assumes those URLs use TLS).
-
Updated this repo to the latest Sync Gateway Versions:
install-sync-gatewaynow installs Sync Gateway Enterprise and Sync Gateway Community2.7.3.
-
Updated this repo to work with AWS Provider 3.x:
- The
couchbase-clustermodule now sets theignore_changeslifecycle setting onload_balancersandtarget_group_arnsattributes. As of AWS Provider 3.x, if you useaws_autoscaling_attachment, you MUST haveignore_changesset on these attributes, or your load balancer will be removed (see corresponding issue in the AWS provider). Since thecouchbase-clustermodule 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-grouphas been updated to use the new syntax for theaws_alb_listener_ruleresource. In addition to thepath-patternrules you could pass in viarouting_condition, you can now also pass inhost-header,http-request-method, andsource-iprules.
- 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_retryfunction (e.g., in your User Data scripts), we recommend updating theexpected_messageparameter (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-clustermodule using the new input variablesinstance_role_pathandinstance_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.