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
@@ -1,20 +0,0 @@
|
||||
#!/usr/bin/env bash
|
||||
set -eo pipefail
|
||||
[[ $DOKKU_TRACE ]] && set -x
|
||||
source "$PLUGIN_CORE_AVAILABLE_PATH/common/functions"
|
||||
|
||||
trigger-openresty-vhosts-proxy-supports-routes() {
|
||||
declare desc="advertises path-based routing support for openresty (currently false)"
|
||||
declare trigger="proxy-supports-routes"
|
||||
declare APP="$1"
|
||||
|
||||
if [[ "$(plugn trigger proxy-type "$APP")" != "openresty" ]]; then
|
||||
return
|
||||
fi
|
||||
|
||||
# The openresty sidecar image does not yet accept path-prefix routing labels.
|
||||
# Tracked upstream at dokku/openresty-docker-proxy#137.
|
||||
echo "false"
|
||||
}
|
||||
|
||||
trigger-openresty-vhosts-proxy-supports-routes "$@"
|
||||
Reference in new issue
Block a user