Releases: cloudposse/terraform-aws-components
Disable TLS by default
What
- Disable TLS for document DB
Why
- Codefresh does not support TLS connection to MongoDB
Migration note
Remember that the changes require document DB instances reboot,
so after terraform apply the changes will become in-sync
after the next maintenance window
or you have to reboot the instances manually.
0.69.1 Fix `elasticache_redis_host` output
what
- Fix
elasticache_redis_host
output
why
- Copy-paste from another output
0.69.0 Bump `terraform-aws-codefresh-backing-services` version
what
- Bump
terraform-aws-codefresh-backing-services
version
why
0.68.0: Support deploying kops cluster into shared VPC
[kops][kops-aws-platform][vpc] Support deploying kops cluster into shared VPC (#158)
0.67.0 Add `kops-legacy-account-vpc-peering`
what
- Add
kops-legacy-account-vpc-peering
project
why
- Provision VPC peering connection between a
kops
VPC and a legacy VPC in a different AWS account (possibly provisioned manually without using Terraform or other automation tools) - Specify what parameters are needed from the legacy AWS account to be able to provision a VPC peering connection
- Show the IAM role, policies and permissions required in the legacy account
0.66.0: [kops][vpc] Create VPC by itself and have kops adopt it
[kops][vpc] Create VPC by itself and have kops
adopt it (#153)
0.65.0: Subnets tagging (#156)
* Subnets tagging * Pin the version
0.64.1: Fix avilability zone (#154)
* Fix avilability zone * Fix formatting * Fix subnets
0.64.0
0.63.0
what
Use the output value from #121
to set a local
variable.
The local
value can then be used in individual invocations of https://github.com/cloudposse/terraform-aws-iam-user which will occur in a later change
why
We currently do not set the default password length when calling https://github.com/cloudposse/terraform-aws-iam-user
The plan is to change our usage of this module to include this AWS account-level dynamic value.