Releases: cloudposse/terraform-aws-elasticache-redis
v1.10.0
feat: Expose Transit Encryption Mode as Output @milldr (#266)
## what - Add output for transit encryption mode in outputs.tfwhy
- We want to expose this output for reference
references
.
🤖 Automatic Updates
chore(deps): update terraform cloudposse/cloudwatch-logs/aws to v0.6.9 @[renovate[bot]](https://github.com/apps/renovate) (#255)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/cloudwatch-logs/aws (source) | module | patch | 0.6.8 -> 0.6.9 |
Release Notes
cloudposse/terraform-aws-cloudwatch-logs (cloudposse/cloudwatch-logs/aws)
v0.6.9
🐛 Bug Fixes
allow underscores in names @cornfeedhobo (#66)
what
- allow underscores in log group names
why
- I created a lambda with underscores in the name, which is auto-creating a log group to match, yet the cloudposse lambda module was creating a group without underscores, which was useless.
references
🤖 Automatic Updates
Migrate new test account @osterman (#63)
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/settings.yml @osterman (#62)
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
Update release workflow to allow pull-requests: write @osterman (#61)
what
- Update workflow (
.github/workflows/release.yaml
) to have permission to comment on PR
why
- So we can support commenting on PRs with a link to the release
Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#60)
what
- Update workflows (
.github/workflows
) to use shared workflows from.github
repo
why
- Reduce nested levels of reusable workflows
Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#59)
what
- Update workflows (
.github/workflows
) to addissue: write
permission needed by ReviewDogtflint
action
why
- The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @osterman (#58)
what
- Update workflows (
.github/workflows/settings.yaml
)
why
- Support new readme generation workflow.
- Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#57)
what
- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.github
repository - Simplify management of workflows from centralized hub of configuration
Add GitHub Settings @osterman (#56)
what
- Install a repository config (
.github/settings.yaml
)
why
- Programmatically manage GitHub repo settings
Update README.md and docs @cloudpossebot (#53)
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
Update Scaffolding @osterman (#54)
what
- Reran
make readme
to rebuildREADME.md
fromREADME.yaml
- Migrate to square badges
- Add scaffolding for repo settings and Mergify
why
- Upstream template changed in the
.github
repo - Work better with repository rulesets
- Modernize look & feel
Update README.md and docs @cloudpossebot (#51)
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
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 is behind base branch, 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.
v1.9.2
Fix Compatibility issue with Terraform AWS Provider v6.0.0 @ngoyal16 (#261)
## whatFix Compatibility issue with Terraform AWS Provider v6.0.0
why
A breaking change introduced in Terraform AWS Provider v6.0.0 prevents deploying Redis instances when auth_token is not specified.
references
closes #260
🤖 Automatic Updates
v1.9.1
🚀 Enhancements
bump aws provider version to support valkey engine on other resource types @joe-niland (#257)
## what- Update AWS provider version to 5.73.0
why
- When specifying
valkey
in theengine
version, the apply fails because this engine value is not supported on theaws_elasticache_replication_group
resource
references
- None
v1.9.0
v1.8.0
[FEAT] add `global_replication_group_id` support @miguelzenteno (#253)
## what- adds support for the
global_replication_group_id
attribute - updates code to set other attributes to
null
whenglobal_replication_group_id
is set.
why
- We want to use
elasticache_global_replication_group
along side this module to manage global datastores - When this attribute is set, the cluster will be set as a secondary for the global datastore
references
v1.7.1
feat: add snapshot_arns_to_restore for serverless ElastiCache @muhammadasgharaliqureshi (#252)
## What & Why- Adds a new variable
serverless_snapshot_arns_to_restore
that allows restoring a serverless ElastiCache Redis cluster from an existing snapshot. - References Issue #251
- This capability is essential for users migrating from a serverful Redis cluster to serverless via snapshot restore.
References
Example Usage
module "redis_serverless" {
source = "cloudposse/elasticache-redis/aws"
# existing variables ...
serverless_enabled = true
serverless_snapshot_arns_to_restore = ["arn:aws:s3:::my-snapshot-bucket/redis-snapshot.rdb"]
}
Testing
- Ran terraform validate on the module; no errors.
- Executed terraform plan using the examples/ folder with this new variable set, and verified it passed.
- Confirmed that when specifying serverless_snapshot_arns_to_restore, the argument is included in the aws_elasticache_serverless_cache.default resource.
Testing Results
tofu init
tofu plan
Checklist
- Added new variable serverless_snapshot_arns_to_restore in variables.tf
- Updated aws_elasticache_serverless_cache.default in main.tf to pass the variable
- Documented usage in the README (or relevant doc files)
- Passed terraform fmt and terraform validate
- Awaiting maintainer feedback
🤖 Automatic Updates
chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @[renovate[bot]](https://github.com/apps/renovate) (#221)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/dynamic-subnets/aws (source) | module | patch | 2.4.1 -> 2.4.2 |
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.2
🚀 Enhancements
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @renovate (#191)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/utils/aws (source) | module | minor | 1.3.0 -> 1.4.0 |
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0
Add il-central-1 region @​jasonmk (#​31)
what
Add new Tel Aviv (il-central-1) region
why
Provide full coverage
references
Sync github @​max-lobur (#​27)
Rebuild github dir from the template
🤖 Automatic Updates
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @renovate (#191)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/utils/aws (source) | module | minor | 1.3.0 -> 1.4.0 |
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0
Add il-central-1 region @​jasonmk (#​31)
what
Add new Tel Aviv (il-central-1) region
why
Provide full coverage
references
Sync github @​max-lobur (#​27)
Rebuild github dir from the template
Update README.md and docs @cloudpossebot (#189)
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
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 is behind base branch, 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.
v1.7.0 Add support for Valkey cache
This release adds a new input, engine
, which you can set to redis
(the default) or valkey
to choose which cache engine you want to use.
feat: Add support for Valkey engine @adamantike (#249)
## whatThis change allows setting the engine
variable, to allow using Valkey as the cache engine.
No breaking changes are expected, as the default value for the engine
variable is set to redis
. Also, the minimum AWS provider version is not changed as using Redis does not require using a newer provider.
references
v1.6.0
v1.5.0
🚀 Enhancements
Allow config endpoint as reader endpoint output @justinfranco (#245)
## what This avoids a situation where the reader endpoint tries to use `coalesce(null, null, null)` when in cluster mode and instead uses the configuration endpoint.why
When using cluster mode there is no reader endpoint so the output tries to use coalesce(null, null, null)
which results in a plan error. As outlined in the AWS docs the config endpoint should be used instead when in cluster mode.
references
Closes #236
chore(deps): bump github.com/hashicorp/go-getter from 1.7.4 to 1.7.5 in /test/src in the go_modules group across 1 directory @dependabot (#246)
Bumps the go_modules group with 1 update in the /test/src directory: [github.com/hashicorp/go-getter](https://github.com/hashicorp/go-getter).Updates github.com/hashicorp/go-getter
from 1.7.4 to 1.7.5
Release notes
Sourced from github.com/hashicorp/go-getter's releases.
v1.7.5
What's Changed
- Prevent Git Config Alteration on Git Update by
@dduzgun-security
in hashicorp/go-getter#497New Contributors
@dduzgun-security
made their first contribution in hashicorp/go-getter#497Full Changelog: hashicorp/go-getter@v1.7.4...v1.7.5
Commits
5a63fd9
Merge pull request #497 from hashicorp/fix-git-update5b7ec5f
fetch tags on update and fix tests9906874
recreate git config during update to prevent config alteration- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version
will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version
will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>
will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>
will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>
will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the Security Alerts page.
🤖 Automatic Updates
chore(deps): bump github.com/hashicorp/go-getter from 1.7.4 to 1.7.5 in /test/src in the go_modules group across 1 directory @dependabot (#246)
Bumps the go_modules group with 1 update in the /test/src directory: [github.com/hashicorp/go-getter](https://github.com/hashicorp/go-getter).Updates github.com/hashicorp/go-getter
from 1.7.4 to 1.7.5
Release notes
Sourced from github.com/hashicorp/go-getter's releases.
v1.7.5
What's Changed
- Prevent Git Config Alteration on Git Update by
@dduzgun-security
in hashicorp/go-getter#497New Contributors
@dduzgun-security
made their first contribution in hashicorp/go-getter#497Full Changelog: hashicorp/go-getter@v1.7.4...v1.7.5
Commits
5a63fd9
Merge pull request #497 from hashicorp/fix-git-update5b7ec5f
fetch tags on update and fix tests9906874
recreate git config during update to prevent config alteration- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version
will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version
will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>
will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>
will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>
will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this...
v1.4.1
🚀 Enhancements
fix: Default transit_encryption_mode to null if var.transit_encryption_enabled is false @amontalban (#238)
what
Fixing this problem when var.transit_encryption_enabled
is false
the transit_encryption_mode
value should be null.
why
I was blindsided with my use case of encrypting everything and I should have covered the default use case.