-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Replace deprecated is_enabled with state in EventBridge rules #119
Conversation
+1 for moving fw with this PR. |
@antonbabenko this looks like quick fix and easy to adopt in the module. It will allow all of us to stop be annoyed by the constant warnings during TF plan/apply. |
Co-authored-by: Anton Babenko <anton@antonbabenko.com>
## [3.3.0](v3.2.4...v3.3.0) (2024-04-23) ### Features * Replace deprecated is_enabled with state in EventBridge rules ([#119](#119)) ([920138a](920138a))
This PR is included in version 3.3.0 🎉 |
Great news! Thank you for prompt response. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Updated the aws_cloudwatch_event_rule resource definition in the Terraform configuration to replace the deprecated is_enabled attribute with the state attribute. This change ensures compatibility with the latest versions of the AWS provider.
Motivation and Context
This change is required to address deprecation warnings from the AWS provider for Terraform. The use of is_enabled has been deprecated and replaced by state, which is now required to define the enabled or disabled status of CloudWatch Event Rules.
Resolving this prevents potential issues with future versions of the AWS provider that may no longer support the is_enabled attribute, ensuring the stability and maintainability of the infrastructure code.
Breaking Changes
This change does not break backwards compatibility with the current major version of the module, as it merely replaces a deprecated attribute with its recommended alternative.
Users who rely on older versions of the AWS provider (before the introduction of the state attribute) should consider upgrading their provider to continue using this module.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request[INFO] Initializing environment for https://github.com/antonbabenko/pre-commit-terraform.
[INFO] Installing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
Terraform fmt............................................................Passed
Terraform docs...........................................................Passed
Terraform validate with tflint...........................................Passed
Terraform validate.......................................................Passed
check for merge conflicts................................................Passed
fix end of files.........................................................Passed
trim trailing whitespace.................................................Passed