[Feature] Implement a blocked servers list #1896
Merged
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.
📃 Description
This PR implements a "blocked server" list. The "allow" list set in
SPEEDTEST_SERVERSwill take precedent over the "blocked" list set inSPEEDTEST_BLOCKED_SERVERS.🪵 Changelog
➕ Added
SPEEDTEST_BLOCKED_SERVERSenvironment variable, this should be a comma separated list of server IDs likeSPEEDTEST_BLOCKED_SERVERS="1234,09876,15432".🧜♀️ Process Map
flowchart TD A[Select server job] --> B{Server exists?} B -->|Yes| Z B -->|No| C{Has config servers?} C -->|Yes| D(Choose a random server from the list) D --> X(Update server) X --> Z C -->|No| E{Blocked list present?} E -->|No| Z E -->|Yes| F(Get server list and filter blocked list) F --> G(Pick the first server from the list) G --> Y(Update server) Y --> Z(End job)