0d4560177a
Rather than removing all port mappings, we simply remap port 80 mappings to 443. The previous behavior would remove custom port mappings for all applications and reset them on any certificate change, preventing automation from plugins such as letsencrypt. While this behavior doesn't matter for buildpack deploys - which only expose a single port on container port 5000 - Dockerfile deploys would frequently be affected by such a change, requiring a remapping of all custom ports. This commit also standardizes on the method used to source the proxy functions
25 lines
737 B
Bash
Executable File
25 lines
737 B
Bash
Executable File
#!/usr/bin/env bash
|
|
set -eo pipefail; [[ $DOKKU_TRACE ]] && set -x
|
|
source "$PLUGIN_CORE_AVAILABLE_PATH/common/functions"
|
|
source "$PLUGIN_AVAILABLE_PATH/proxy/functions"
|
|
source "$PLUGIN_AVAILABLE_PATH/config/functions"
|
|
|
|
proxy_ports_remove_cmd() {
|
|
declare desc="remove specific proxy port mappings from an app"
|
|
local cmd="proxy:ports-remove"
|
|
local APP="$2"; verify_app_name "$APP"
|
|
shift 2
|
|
|
|
local INPUT_PORTS="$*"
|
|
if [[ -z "$INPUT_PORTS" ]]; then
|
|
dokku_log_warn "No port mapping specified. Please supply a valid configured host port"
|
|
list_app_proxy_ports "$APP"
|
|
dokku_log_fail "exiting..."
|
|
fi
|
|
|
|
remove_proxy_ports "$APP" "$@"
|
|
plugn trigger post-proxy-ports-update "$APP" "remove"
|
|
}
|
|
|
|
proxy_ports_remove_cmd "$@"
|