[IMP] bantracking: use system parameter for max notification attempts #45
Conversation
This file contains hidden or 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
IrvingReyes
force-pushed
the
16.0-set-max-attempts-system-param-irvingreyes
branch
4 times, most recently
from
a92b6b4 to
8acb145
Compare
Replace the hardcoded attempts value in the scheduled action with a configurable system parameter, `bantracking.max_notification_attempts`. The domain is updated accordingly to filter logs using the retrieved parameter value. This improves maintainability and allows operators to adjust retry behavior without modifying code.
IrvingReyes
force-pushed
the
16.0-set-max-attempts-system-param-irvingreyes
branch
from
8acb145 to
67f4e60
Compare
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.
Related MR
Replace the hardcoded attempts value in the scheduled action with
a configurable system parameter, bantracking.max_notification_attempts.
The domain is updated accordingly to filter logs using the retrieved
parameter value. This improves maintainability and allows operators
to adjust retry behavior without modifying code.