refactor: export applicator singletons from egress_apply backends
test / unit (pull_request) Successful in 35s
test / integration (pull_request) Successful in 21s
lint / lint (push) Successful in 1m44s
test / unit (push) Successful in 32s
test / integration (push) Successful in 19s
Update Quality Badges / update-badges (push) Successful in 1m17s

Replace module-level apply_routes_change wrappers with a public
applicator singleton in each backend. Callers now work with the
EgressApplicator instance directly (applicator.apply_routes_change)
rather than through a function shim.
This commit was merged in pull request #248.
This commit is contained in:
2026-06-23 20:39:05 +00:00
parent 77bdaf0a96
commit 200306f1cf
5 changed files with 24 additions and 39 deletions
+2 -10
View File
@@ -49,20 +49,12 @@ class DockerEgressApplicator(EgressApplicator):
)
_applicator = DockerEgressApplicator()
def apply_routes_change(slug: str, content: str) -> tuple[str, str]:
return _applicator.apply_routes_change(slug, content)
validate_routes_content = EgressApplicator.validate_routes_content
applicator = DockerEgressApplicator()
__all__ = [
"DockerEgressApplicator",
"EgressApplyError",
"apply_routes_change",
"applicator",
"fetch_current_routes",
"validate_routes_content",
]