Add optional random server selection for TCP and HTTP backends #198
+6
−2
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.
Introduced a new setting MJML_TCPSERVERS_RANDOM and MJML_HTTPSERVERS_RANDOM for server selection, allowing random server selection to be toggled. This makes it possible to either use the servers in order or randomly.
Both settings default to True, enabling random selection by default, but can be set to False to maintain a fixed order of servers.
Refactored the
mjml/tools.py
file to shuffle the servers list based on the new settings for both TCP and HTTP backends.