Releases: cloudposse-terraform-components/aws-efs
v1.537.1
🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#38)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
chore(deps): update terraform cloudposse/efs/aws to v1.2.0 @[renovate[bot]](https://github.com/apps/renovate) (#37)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/efs/aws (source) | module | minor | 1.1.0 -> 1.2.0 |
Release Notes
cloudposse/terraform-aws-efs (cloudposse/efs/aws)
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 options
why
See https://github.com/cloudposse/terraform-aws-efs/issues/132
references
closes #132
🤖 Automatic Updates
Replace Makefile with atmos.yaml @osterman (#152)
what
- Remove
Makefile
- Add
atmos.yaml
why
- Replace
build-harness
withatmos
for 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
files
why
- Re-apply
.github/settings.yml
from 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
files
why
- Re-apply
.github/settings.yml
from org level to getterratest
environment - Migrate to new
test
account
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
Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#147)
what
- Update workflows (
.github/workflows
) to use shared workflows from.github
repo
why
- Reduce nested levels of reusable workflows
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Enable merge queue @goruha (#36)
## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners fileswhy
- Support auto merge PRs
- Create merge queue
- Implement new CodeOwners policy
v1.537.0
🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#33)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#32)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
chore(deps): update terraform cloudposse/efs/aws to v1 @[renovate[bot]](https://github.com/apps/renovate) (#9)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/efs/aws (source) | module | major | 0.36.0 -> 1.1.0 |
Release Notes
cloudposse/terraform-aws-efs (cloudposse/efs/aws)
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_egress
which 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
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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#31)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
chore(deps): update terraform cloudposse/efs/aws to v0.36.0 @[renovate[bot]](https://github.com/apps/renovate) (#5)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/efs/aws (source) | module | minor | 0.35.0 -> 0.36.0 |
Release Notes
cloudposse/terraform-aws-efs (cloudposse/efs/aws)
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 @&#̴...
v1.536.1
Added tests @goruha (#19)
## what * Added testsSummary by CodeRabbit
-
New Features
- Added configuration for Elastic File System (EFS) component
- Introduced new Atmos CLI configuration
- Added DNS primary and delegated configurations
- Created VPC configuration
- Added account mapping configuration and related components
- Introduced new configuration for disabled EFS component
-
Chores
- Updated module versions for remote state
- Updated Go module dependencies
- Added new test fixtures and configurations
- Removed obsolete test script
-
Tests
- Added comprehensive test suite for EFS component
- Introduced new testing configurations and infrastructure
🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#20)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
v1.536.0
fix: Replace deprecated splat expression with [*] for Terraform 1.5.6… @sushmithakumar (#18)
## Terraform 0.12.0+ Splat Operator Updates ## What Updated Terraform configuration to replace legacy splat syntax(resource.*.attribute)
with modern bracket-based expressions (resource[*].attribute).
Incorporated for expressions where applicable to improve flexibility and readability.
No functional changes to infrastructure; these updates are syntax improvements.
Why
Aligns with Terraform 0.12.0+ enhancements and first-class expression support.
Improves readability and maintainability of Terraform code.
Prevents potential deprecation warnings by replacing outdated syntax.
References
Terraform v0.12.0 Upgrade Guide
Summary by CodeRabbit
- Refactor
- Updated AWS IAM policy document syntax for accessing data source elements
- Refined method of constructing principal identifiers in IAM policy