chore(deps): update terraform cloudposse/cloudwatch-events/aws to v0.9.1 (main)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/cloudwatch-events/aws (source)	module	minor	0.6.1 -> 0.9.1

---

Release Notes

cloudposse/terraform-aws-cloudwatch-events (cloudposse/cloudwatch-events/aws)

v0.9.1

Compare Source

Remove `cloudwatch_event_rule_is_enabled` usage because of deprecation @​kirylkaminski (#​44)

what

• Added state attribute to aws_cloudwatch_event_rule.this resource which is a replacement for the deprecated is_enabled
• Added cloudwatch_event_rule_state variable for it
• Added logic to allow usage of deprecated variable if non-default value specified (is_enabled true/false maps to state ENABLED/DISABLED)

why

• Because it still shows deprecation warning when running the module

references

• closes #​36

chore: update terratest dependency @​RoseSecurity (#​45)

what

• Update the Terratest dependencies to support Opentofu
• Ran the following commands to update test dependencies:

go get github.com/gruntwork-io/[email protected]
go mod tidy

testing

• Ensured the tests still worked with:

go test -v -timeout=1h

why

• OpenTofu tests are failing in these pipelines because the version of Terratest does not support OpenTofu in the terraform module. ≥ v0.46.0 includes native OpenTofu support

references

• Terratest Release

🤖 Automatic Updates

Fix go version in tests @​osterman (#​43)

what

• Update go 1.24

why

• Error loading shared library libresolv.so.2 in Go 1.20

References

• https://sweetops.slack.com/archives/G014YEKDH4K/p1746672149263629
• https://github.com/golang/go/issues/59305#issuecomment-1488478737
• https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/pull/294/#issuecomment-2859195553

Replace Makefile with atmos.yaml @​osterman (#​42)

what

• Remove Makefile
• Add atmos.yaml

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

Migrate new test account @​osterman (#​41)

what

• Update .github/settings.yml
• Update .github/chatops.yml files

why

• Re-apply .github/settings.yml from org level to get terratest 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 (#​40)

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

v0.9.0

Compare Source

feat: Add missed tags @​MaxymVlasov (#​39)

what

Add tags to resources where they missed

🤖 Automatic Updates

Update .github/settings.yml @​osterman (#​38)

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 (#​35)

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 (#​34)

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 (#​32)

what

• Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @​osterman (#​31)

what

• Update workflows (.github/workflows/settings.yaml)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​30)

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 (#​29)

what

• Install a repository config (.github/settings.yaml)

why

• Programmatically manage GitHub repo settings

Update Scaffolding @​osterman (#​27)

what

• Reran make readme to rebuild README.md from README.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

v0.8.0

Compare Source

added support for role_arn in cloudwatch events for specifying roles @​jfishzon (#​26)

what

• added role_arn to be able to specify a specific role for when dealing with sending events cross-account

why

• lacks support for role_arn when the target requires a different role

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_event_rule#role_arn

• closes #​25

v0.7.0

Compare Source

What's Changed

• git.io->cloudposse.tools update by @​dylanbannon in #​14
• Sync github by @​max-lobur in #​18
• chore: update label module by @​dudymas in #​24

Full Changelog: cloudposse/terraform-aws-cloudwatch-events@0.6.1...0.7.0

Important (Potentially Breaking) Changes

• The label for the cluster has been updated to the latest null-label module. This means that tenant is now an expected field and will likely cause disruptive name changes when upgrading. Take care updating the fields in context.tf so that you aren't impacted. Most likely you'll need to look at the label_order field if you need to exclude the tenant field from the label.

---

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.

[mergify]

/terratest