dynamic_routes
Skill3 starsChanged 3 months agoMITView on GitHub
Okapi can enable/disable individual routes, whole groups, and OpenAPI documentation at runtime. Disabled routes respond with 404 — no redeploy required, and the OpenAPI document refreshes automatically. Deprecated() keeps the route active but tags it in OpenAPI so clients see a warning. Combine with Hide() to remove it from docs entirely. Group-level: Toggle routes from config without restarting the process: Capture the routes you want to toggle when you register them; o.Routes() returns a snapshot (copy) of Route values, so…
In this repository20 other files it gives its agents.
- authenticationSkill
- cliSkill
- contextSkill
- error_handlingSkill
- http_clientSkill
- middlewareSkill
- openapiSkill
- overviewSkill
- request_bindingSkill
- responseSkill
- route_definitionSkill
- routingSkill
- sse_streamSkill
- std_compatSkill
- templatingSkill
- testingSkill
- tls_httpsSkill
- validationSkill
- websocketSkill
- web_spaSkill
The file
Files
Okapi Dynamic Routes
Okapi can enable/disable individual routes, whole groups, and OpenAPI documentation at runtime. Disabled routes respond with 404 — no redeploy required, and the OpenAPI document refreshes automatically.
Disabling / Enabling a Single Route
route := o.Get("/admin/console", adminHandler)
route.Disable() // requests now get 404
route.Enable() // back onlineDisabling / Enabling a Whole Group
admin := o.Group("/admin", jwtAuth.Middleware)
admin.Get("/users", listUsers)
admin.Get("/audit", listAudit)
admin.Disable() // every route under /admin is 404
admin.Enable()Toggling OpenAPI Documentation at Runtime
o.WithOpenAPIDisabled() // /docs, /swagger, /redoc, /scalar, /openapi.* return 404
// Bring them back
o.WithOpenAPIDocs(okapi.OpenAPI{Title: "My API", Version: "1.0.0"})Marking a Route Deprecated
Deprecated() keeps the route active but tags it in OpenAPI so clients see a warning. Combine with Hide() to remove it from docs entirely.
o.Get("/v1/books", legacyHandler).Deprecated()
o.Get("/internal/metrics", metricsHandler).Hide()Group-level:
v1 := o.Group("/api/v1").Deprecated() // all routes flagged deprecatedFeature Flag Pattern
Toggle routes from config without restarting the process:
type Toggles struct {
BetaSearch bool
Sandbox bool
}
func registerRoutes(o *okapi.Okapi, t *Toggles) {
search := o.Get("/search", searchHandler)
sandbox := o.Group("/sandbox", devOnlyMiddleware)
sandbox.Get("/echo", echoHandler)
apply := func() {
if t.BetaSearch { search.Enable() } else { search.Disable() }
if t.Sandbox { sandbox.Enable() } else { sandbox.Disable() }
}
apply() // initial state
// Re-call apply() whenever t changes (config reload, admin endpoint, etc.)
}Admin Endpoint to Toggle Routes
Capture the routes you want to toggle when you register them; o.Routes() returns a snapshot (copy) of Route values, so iterating it cannot mutate the live registry.
type RouteToggle struct {
Path string `json:"path" required:"true"`
Enabled bool `json:"enabled"`
}
func wireToggles(o *okapi.Okapi) {
registry := map[string]*okapi.Route{
"/beta/search": o.Get("/beta/search", searchHandler),
"/sandbox": o.Get("/sandbox", sandboxHandler),
}
o.Post("/admin/routes/toggle", okapi.H(func(c *okapi.Context, in *RouteToggle) error {
route, ok := registry[in.Path]
if !ok {
return c.AbortNotFound("route not found")
}
if in.Enabled { route.Enable() } else { route.Disable() }
return c.OK(okapi.M{"path": in.Path, "enabled": in.Enabled})
}))
}
o.Routes()returns a snapshot of registered routes for introspection — useful for listing/exposing what exists, not for mutating state.
When Documentation Refreshes
The OpenAPI document is rebuilt lazily, so the next request to /openapi.json (or any UI route) reflects the current enable/disable state and any newly added webhooks. No cache invalidation step is needed.
Hiding from Docs (Without Disabling)
o.Get("/internal/health", healthHandler).Hide() // still serves traffic, omitted from docs
o.Get("/internal/health", healthHandler, okapi.DocHide())Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

