Skip to content

Releases: ministryofjustice/cloud-platform-terraform-rds-instance

4.7

21 Oct 12:17
abd81d4
Compare
Choose a tag to compare
4.7

Introduces a policy that's limited to snapshot management.

4.6

05 Sep 13:02
3a4e4e6
Compare
Choose a tag to compare
4.6

In this release SSL is set default to "True"

4.5

08 Jul 12:47
3873852
Compare
Choose a tag to compare
4.5

This release introduces the rds_family variable.
RDS families define what configuration the Database is going to use. RDS families and postgresql version must be compatible.

For any Postgresql version, there is a matching RDS family :

  • postgres9.4
  • postgres9.5
  • postgres9.6
  • postgres10
  • postgres11

This is how the module is now invoked:

module "example_team_rds" {
  source = "github.com/ministryofjustice/cloud-platform-terraform-rds-instance"

  // The first two inputs are provided by the pipeline for cloud-platform. See the example for more detail.

  cluster_name           = "cloud-platform-live-0"
  cluster_state_bucket   = "live-0-state-bucket"
  db_allocated_storage   = "20"
  db_instance_class      = "db.t2.small"
  db_iops                = "1000"
  team_name              = "example-repo"
  business-unit          = "example-bu"
  application            = "exampleapp"
  is-production          = "false"
  environment-name       = "development"
  infrastructure-support = "[email protected]"
  rds_family             = "postgres10"

  providers = {
    # This can be either "aws.london" or "aws.ireland:
    aws = "aws.london"
  }
}

Be sure to check this example : rds.tf

4.4

06 Jun 08:54
952bd0f
Compare
Choose a tag to compare
4.4
  • add option to force SSL connections (#32)

4.3

15 May 10:16
a3359d8
Compare
Choose a tag to compare
4.3

This version Includes AllowMajorVersionUpgrade option, a value that indicates whether major version upgrades are allowed.

use "allow_major_version_upgrade" when upgrading the major version of an engine
allow_major_version_upgrade = "true"

4.2

02 May 11:23
eeac8b2
Compare
Choose a tag to compare
4.2

Providers are now defined outside of the module, resolving issue with resource deletion.
This version deprecates the use of the aws_region, in profit of the providers input.

providers expect an existing provider. The example contains two providers, which can then be passed down to the module, as follow:

provider "aws" {
  alias  = "london"
  region = "eu-west-2"
}

provider "aws" {
  alias  = "ireland"
  region = "eu-west-1"
}
module "example_team_rds" {
  ...
  providers = {
    # Can be either "aws.london" or "aws.london"
    aws = "aws.london"
  }
}```

4.1

17 Apr 10:17
f95057f
Compare
Choose a tag to compare
4.1

Apply changes like storage size immediately

4.0

25 Mar 15:58
7562472
Compare
Choose a tag to compare
4.0

This release contains a few changes :

  • it encourage the use of the London region in AWS (eu-west-2)
  • it uses the s3 path structure specific to our Live-1 bucket.

3.1

15 Feb 10:01
ca59418
Compare
Choose a tag to compare
3.1
  • Do not specify a minor version to allow for automatic updates (#15)

3.0

07 Dec 16:31
4ad4b82
Compare
Choose a tag to compare
3.0
  • Prefix master username with alphanumerics (#10)