refactor: drop proxy-supports-routes capability trigger
The trigger was added to refuse proxy:route:set under openresty and haproxy, but the hard refusal created an ordering dependency for declarative tools and blocked users from staging routes ahead of a backend switch. Routes are now stored regardless of the active backend and silently ignored by backends that do not render them; the docs call out the inert behavior under openresty and haproxy.
This commit is contained in:
11 files changed
+8
-167
No files matched your search
@@ -23,15 +23,6 @@ func CommandRouteSet(appName string, processName string, path string, port int,
|
||||
return errors.New("Usage: dokku proxy:route:set <app> <process> <path> [--port <port>] [--strip-prefix]")
|
||||
}
|
||||
|
||||
supported, err := SupportsRoutes(appName)
|
||||
if err != nil {
|
||||
return err
|
||||
}
|
||||
if !supported {
|
||||
proxyType := getComputedProxyType(appName)
|
||||
return fmt.Errorf("path-based routing is not yet supported with the %s proxy backend", proxyType)
|
||||
}
|
||||
|
||||
if port == 0 {
|
||||
port = DefaultRoutePort
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user