f9de91fc4b
The `openresty:report --format json` payload emitted bare property names for the four global-only properties (`image`, `letsencrypt-email`, `letsencrypt-server`, `allowed-letsencrypt-domains-func-base64`), while `hsts` already used the `global-`/`computed-` convention adopted by the other proxy plugins. External tooling consuming the report had to maintain a per-property naming map within a single plugin. The global flag map now emits `--openresty-global-<X>` (raw stored value, empty when unset) and `--openresty-computed-<X>` (effective value with the built-in default applied) for those four properties plus `hsts`, and the per-app map gains the same pair for the global-only properties. The compose template and the two non-report callers consume the `computed-` accessors so the runtime behavior is unchanged.
22 lines
558 B
Bash
Executable File
22 lines
558 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/openresty-vhosts/internal-functions"
|
|
|
|
trigger-openresty-vhosts-certs-force() {
|
|
declare desc="openresty-vhosts certs-force plugin trigger"
|
|
declare trigger="certs-force"
|
|
declare APP="$1"
|
|
|
|
if [[ "$(plugn trigger proxy-type "$APP")" != "openresty" ]]; then
|
|
return
|
|
fi
|
|
|
|
if [[ -n "$(fn-openresty-computed-letsencrypt-email)" ]]; then
|
|
echo true
|
|
fi
|
|
}
|
|
|
|
trigger-openresty-vhosts-certs-force "$@"
|