Releases: zachreborn/terraform-modules
Releases · zachreborn/terraform-modules
v2.7.1
What's Changed
- removed legacy s3 modules which have been replaced by better s3/bucket code by @zachreborn in #7
Full Changelog: v2.7.0...v2.7.1
Contributors
zachreborn
Assets 2
v2.7.0
What's Changed
- Security Hub and Security Hub for organization modules by @zachreborn in #6
Full Changelog: v2.6.0...v2.7.0
Contributors
zachreborn
Assets 2
v2.6.0
Contributors
zachreborn
Assets 2
v2.5.0
Contributors
zachreborn
Assets 2
v2.4.5
Contributors
zachreborn
Assets 2
v2.4.4
Contributors
zachreborn
Assets 2
v2.4.3
Full Changelog: v2.4.2...v2.4.3
v2.4.2
Overview
Since we first began working on terraform modules, terraform has changed a lot and so have we! This update begins a new major version which will not be backward compatible with v1. In part, this is because we're exclusively supporting terraform >=v1.0 and it also is because we needed to do some tidying up of our code and folder structure.
Highlights
- Going forward, modules for a major service will be within a folder structure indicating the service. This means that many modules have moved down a level in the following format './module_long_name' will be moving to './module/name'. Examples:
- ./route53_zone -> ./route53/zone
- ./route53_record -> ./route53/simple_record
- ./fortigate_firewall -> ./vendor/fortigate_firewall
- ./corelight -> ./vendor/corelight
- ./s3 -> ./s3/bucket
- Modules now use validation
- Variables are now using validation where applicable to provide better feedback through unit testing for each module.
- CI/CD automation improvements
- The CI/CD automation has been improved and moved to Github Actions. This is to simplify the workflows and have more direct integration with engineers and developers working on deployments.
- test.yml now tests the terraform code as well as lints it
- build.yml now generates terraform-docs and formats the code with 'terraform fmt -recursive'
- README updates
- You'll notice the readme has a new robot overseeing our work. We wanted to create a little mascot for something fun.
- We're using the 'Best-README-Template' customized to our liking. Be sure to check it out at https://github.com/othneildrew/Best-README-Template if you'd like to utilize this excellent readme.
What that means for you
- Can only impact existing AWS resources
- Less than 10% of existing AWS resources will be unable to be upgraded
- These resources will need to be either rebuilt on the latest, or removed from terraform state and re-imported in with the latest version over the next year or so
- If you upgrade existing AWS resources, be sure to validate that the folder structure for the source has not moved. If it still errors, verify that the argument or variable names haven't changed. If you still have errors, please open an issue and we'll resolve ASAP.
What's Changed
- dev v2.0 overhaul by @zachreborn in thinkstack-co/terraform-modules#129
- Dev s3 website 2023 update by @zachreborn in thinkstack-co/terraform-modules#131
- added a period to the validation to allow website and domain names as bucket names by @zachreborn in thinkstack-co/terraform-modules#132
- Dev s3 lifecycle by @jakeasarus in thinkstack-co/terraform-modules#115
- added ami validation fix for older ami IDs by @zachreborn in thinkstack-co/terraform-modules#136
- initial commit for intelligent tiering resource configuration by @zachreborn in thinkstack-co/terraform-modules#135
- Dev azuread conditional access initiation by @zachreborn in thinkstack-co/terraform-modules#133
- updated the default terraform workspace to ~>1.4.0 by @zachreborn in thinkstack-co/terraform-modules#138
- Dev aws org ou by @zachreborn in #1
Full Changelog: v1.21.0...v2.4.2
Contributors
zachreborn and Jakeasaurus