Releases: cloudposse/terraform-aws-efs
v1.4.0
feat: add support for IPv6 and dual-stack EFS mount targets @ngoyal16 (#163)
## what- Added support for dual-stack (IPv4 and IPv6) EFS mount targets.
- Introduced mount_target_ip_address_type variable to select between IPV4_ONLY, IPV6_ONLY, and DUAL_STACK.
- Introduced mount_target_ipv6_address variable to specify a custom IPv6 address.
- Updated aws_efs_mount_target resource to utilize the new variables and apply conditional logic for IP assignment.
- Added mount_target_ipv6_addresses output to expose the assigned IPv6 addresses.
why
- The new version of AWS EFS supports dual-stack endpoints, allowing for better compatibility with IPv6-enabled environments.
- Users need the ability to configure the IP address type and provide specific IPv6 addresses if required.
references
Contributors
Assets 2
v1.3.0
feat: add preserve_security_group_id support @oycyc (#161)
## What * Added support for `preserve_security_group_id` variable from the cloudposse/security-group moduleWhy
There are many times where we'd like to preserve the existing security group and update in place, rather than create a new SG and have the rules there.
Default is false, which is the existing behaviors of the module. Does NOT have any diff in any previous code upgrading versions.
References
Contributors
Assets 2
v1.2.1
docs: `elastic` is a valid throughput mode! @oycyc (#158)
`elastic` is a valid throughput mode!closes #151
See Terraform AWS Provider docs: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/efs_file_system#throughput_mode-3
This is also the recommended EFS type by AWS
🤖 Automatic Updates
Contributors
Assets 2
v1.2.0
🚀 Enhancements
132: add transition_to_archive @jgournet (#144)
## what Add transition_to_archive, same as transition_to_ia Also add 180, 270 and 365 days optionswhy
See #132
references
closes #132
🤖 Automatic Updates
Replace Makefile with atmos.yaml @osterman (#152)
## what - Remove `Makefile` - Add `atmos.yaml`why
- Replace
build-harnesswithatmosfor readme genration
References
- DEV-3229 Migrate from build-harness to atmos
Add GitHub Settings @osterman (#141)
## what - Install a repository config (`.github/settings.yaml`)why
- Programmatically manage GitHub repo settings
Update GitHub workflows @osterman (#145)
## what - Update workflows (`.github/workflows/settings.yaml`)why
- Support new readme generation workflow.
- Generate banners
Update .github/settings.yml @osterman (#149)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- Re-apply
.github/settings.ymlfrom org level - Use organization level auto-release settings
references
- DEV-1242 Add protected tags with Repository Rulesets on GitHub
Migrate new test account @osterman (#150)
## what - Update `.github/settings.yml` - Update `.github/chatops.yml` fileswhy
- Re-apply
.github/settings.ymlfrom org level to getterratestenvironment - Migrate to new
testaccount
References
- DEV-388 Automate clean up of test account in new organization
- DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
- DEV-386 Update terratest to use new testing account with GitHub OIDC
Contributors
Assets 2
v1.1.0
Make allow_all_egress a variable @dlacosteGFM (#126)
What changes in this PR?
- Default change is nothing (with this PR applied, nobody would have to change anything)
- Makes a new parameter
allow_all_egresswhich defaults tofalse - When creating the security group for the EFS volume, this line makes the security-group have an "allow egress to 0.0.0.0/0" rule entry. This PR makes that a configurable parameter instead
Why make this change?
- EFS doesn't actually do egress, so this really makes no impact difference at all
- ...but during a security audit we have a dangling "why do you allow egress to 0.0.0.0/0 on this?" question with no really good answer (so let's get rid of it as it doesn't do anything anyways)
References
- PCI DSS 3.2.1 rule 1.1.7 - Requirement to review firewall and router rule sets every 6 months
- PCI DSS 3.2.1 rule 1.2.1 - Restrict inbound and outbound traffic to that which is necessary for the environment
Contributors
Assets 2
v1.0.0
🤖 Automatic Updates
chore(deps): update terraform cloudposse/security-group/aws to v2 (main) @renovate (#135)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/security-group/aws (source) | module | major | 1.0.1 -> 2.2.0 |
Release Notes
cloudposse/terraform-aws-security-group (cloudposse/security-group/aws)
v2.2.0
`.editorconfig` Typo @milldr (#50)
what
fixed intent typo
why
should be spelled "indent"
references
https://cloudposse.slack.com/archives/C01EY65H1PA/p1685638634845009
Sync github @max-lobur (#47)
Rebuild github dir from the template
v2.1.0
- No changes
v2.0.1
🐛 Bug Fixes
Properly handle enabled = false @Nuru (#45)
what
- Properly handle
enabled = false
why
- Fixes #43
v2.0.0: Breaking changes
For details about migrating from v1 to v2, read the migration documentation.
Version 1 of this module had a flaw in that it tried to create new security group rules before deleting the old ones, which the Terraform provider does not handle properly and caused most attempted changes to fail. Version 2 resolves this issue by also creating a new security group when the rules change, installing the new rules in the new security group, then changing the security group assignments. Read the README and the migration documentation for more details.
Document migration from v1 to v2 @Nuru (#42)
what
- Document migration from v1 to v2 of this module
- Fix #40
why
- Serious issues exist in v1, causing v2 to have different defaults and new settings. Documentation is needed to guide users on how to upgrade while minimizing service interruptions.
references
- Closes #40
Fixes the link for examples/complete/main.tf @jdmedeiros (#41)
Fixes the link for examples/complete/main.tf on the README.md file.
Contributors
Assets 2
v0.36.0
🤖 Automatic Updates
chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.13.0 (main) @renovate (#136)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/route53-cluster-hostname/aws (source) | module | minor | 0.12.2 -> 0.13.0 |
Release Notes
cloudposse/terraform-aws-route53-cluster-hostname (cloudposse/route53-cluster-hostname/aws)
v0.13.0
- No changes
v0.12.3
Add zone inputs, update tests, add usage @nitrocode (#42)
what
- Add zone inputs, update tests, add usage
why
- Verify zone name exists
- Dynamically retrieve zone name based on data source inputs
references
git.io->cloudposse.tools update @dylanbannon (#40)
what and why
Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.
References
- DEV-143
Update README.md and docs @cloudpossebot (#131)
what
This is an auto-generated PR that updates the README.md and docs
why
To have most recent changes of README.md and doc from origin templates
Contributors
Assets 2
v0.35.0
variables.tf: transition_to_ia -- add AFTER_1_DAY as valid value @michw (#130)
what
- Add
AFTER_1_DAYas a valid value for transition_to_ia - Add
efs_file_system_policyresource
why
AFTER_1_DAYis a valid value for transition_to_ia argument for lifecycle policy.efs_file_system_policyresource was missing.
Sync github @max-lobur (#124)
Rebuild github dir from the template
Contributors
Assets 2
v0.34.0
- No changes
v0.33.0
Groundwork new workflows @max-lobur (#122)
Fix lint/format before workflows rollout