chore(deps): update terraform terraform-aws-modules/autoscaling/aws to v8 - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
terraform-aws-modules/autoscaling/aws (source)	module	major	~> 7.3 -> ~> 8.0

---

Release Notes

terraform-aws-modules/terraform-aws-autoscaling (terraform-aws-modules/autoscaling/aws)

v8.0.0

Compare Source

⚠ BREAKING CHANGES

• Allow multiple traffic source attachments (#​273)

Features

• Allow multiple traffic source attachments (#​273) (3782413)

---

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.

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Lock the module version to a specific version instead of a version range It's recommended to lock the version of Terraform modules to a specific version rather than a version range. This ensures that the infrastructure remains consistent and predictable, and avoids unexpected changes due to module updates. Consider specifying the exact version of the module instead of using a version range. terraform/vault/cluster/autoscaling_group.tf [88] -version = "~> 8.0" +version = "8.0" Suggestion importance[1-10]: 8 Why: Locking the module version to a specific version ensures consistency and predictability in the infrastructure, avoiding unexpected changes due to module updates. This is a best practice for maintaining stable environments.	8