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:
Jose Diaz-Gonzalez committed 2026-11-04 14:56:38 -05:00
1 parent 9153bb5097
commit a4d40becd8
11 files changed
+8 -167

No files matched your search

@@ -1,21 +0,0 @@
#!/usr/bin/env bash
set -eo pipefail
[[ $DOKKU_TRACE ]] && set -x
source "$PLUGIN_CORE_AVAILABLE_PATH/common/functions"
trigger-haproxy-vhosts-proxy-supports-routes() {
declare desc="advertises path-based routing support for haproxy (currently false)"
declare trigger="proxy-supports-routes"
declare APP="$1"
if [[ "$(plugn trigger proxy-type "$APP")" != "haproxy" ]]; then
return
fi
# The byjg/easy-haproxy sidecar image only supports host-based routing.
# Path-prefix routing requires either an upstream change to that sidecar
# or a different config-generation strategy.
echo "false"
}
trigger-haproxy-vhosts-proxy-supports-routes "$@"