[cloudwatch-logs-aggregator] BREAKING CHANGE: Rollback breaking changes for is_enabled variable #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v0.2.2 release contains a breaking change about
is_enabledvariable in spite of a patch version update. Since this change is undesirable considering the abstractness of the module, we made the following changes:is_enabled(boolean) variable to specify whether the rule is enabled"ENABLED"/"DISABLED"for state ofaws_cloudwatch_event_rulestatevariable instead (BREAKING CHANGE for v0.2.2 users, but not so for users before one)