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 Enterprise 6.6.0 and Couchbase Community 6.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 prepends http:// to node URLs that don't already have a prefix when calling the server-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 Community 2.7.3.

• Updated this repo to work with AWS Provider 3.x:

  • The couchbase-cluster module now sets the ignore_changes lifecycle setting on load_balancers and target_group_arns attributes. As of AWS Provider 3.x, if you use aws_autoscaling_attachment, you MUST have ignore_changes set on these attributes, or your load balancer will be removed (see corresponding issue in the AWS provider). Since the couchbase-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 the aws_alb_listener_rule resource. In addition to the path-pattern rules you could pass in via routing_condition, you can now also pass in host-header, http-request-method, and source-ip rules.

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 the expected_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

• #64