Releases: jareware/terraform-utils
Releases · jareware/terraform-utils
v13.1
v13.0
- Add docs on naming conventions to root README
- Use
required_providersto document provider versions per module - Update AMI for
aws_ec2_ebs_docker_hostto Ubuntu 20.04 LTS - Remove deprecated
aws_mailgun_domainmodule - Introduce new
aws_ses_forwardermodule - Update
reprovision_triggerindocker_compose_hostto be diffable byterraform plan
v12.1
v12.0
Fittingly, the v12.0 release upgrades this set of utils to Terraform 0.12 compatibility. 🎉
Short of changes to provider configuration mandated by the Terraform version bump, modules are almost entirely backwards compatible.
Some notes:
name_prefixis now optional for all modules that expected it - if omitted, a random, unique name prefix is used insteadaws_static_siteno longer supports external S3 buckes - it was an unnecessary complication to the module, and the few cases that need the functionality, can simply create their ownaws_reverse_proxyinsteadaws_lambda_apiandaws_lambda_cronjobare now internally implemented using a singleaws_lambda_functionresource - you may want toterraform state mvif upgrading in-placeaws_lambda_apinow has a configurable endpoint type, which defaults toEDGE(previouslyREGIONAL)aws_reverse_proxynow correctly handles authenticated CORS request pre-flightsaws_reverse_proxynow supports anoverride_only_on_codeoption, for limiting the applicability of the otheroverride_*optionsaws_reverse_proxynow defaults to respecting upstream cache control headers (cache_ttl_overridepreviously defaulted to the safer-but-kinda-wrong value0)
v11.0
v10.0
- Remove
aws_internet_vpcmodule, as it's too simplistic to warrant a spot here - Update
aws_static_sitemodule so that its bucket can only be accessed via the CloudFront distribution, not directly - Remove CloudFront from in front of API Gateway in
aws_lambda_apimodule - Add throttling options to
aws_lambda_apimodule - Remove built-in CORS preflight support from
aws_lambda_apimodule; it's simple enough to implement in code, and then we make less assumptions on how the module is used
v9.4
- Rename
aws_tagsto just tags, for uniformity with regular AWS resources - Add a section on debugging the API Gateway to
aws_lambda_apimodule - Add debug options
api_gateway_logging_levelandapi_gateway_cloudwatch_metricstoaws_lambda_apimodule README - Define
aws_api_gateway_stageusing a separate resource, so we can apply tags - Add a description for
aws_api_gateway_rest_api