chore: clarify plugin trigger name

docs/advanced-usage/schedulers/docker-local.md

@@ -25,7 +25,7 @@ This plugin implements various functionality through `plugn` triggers to integra
 - `pre-restore`
 - `scheduler-deploy`
 - `scheduler-docker-cleanup`
-- `scheduler-failed`
+- `scheduler-logs-failed`
 - `scheduler-run`
 - `scheduler-stop`
 - `scheduler-tags-create`

docs/development/plugin-triggers.md

@@ -1207,7 +1207,7 @@ DOKKU_SCHEDULER="$1"; APP="$2"; FORCE_CLEANUP="$3";
 # TODO
 ```
 
-### `scheduler-failed`
+### `scheduler-logs-failed`
 
 > Warning: The scheduler plugin trigger apis are under development and may change
 > between minor releases until the 1.0 release.

plugins/logs/subcommands/failed

@@ -11,7 +11,7 @@ cmd-logs-failed() {
   [[ -z "$APP" ]] && dokku_log_fail "Please specify an app to run the command on"
 
   DOKKU_SCHEDULER=$(config_get "$APP" DOKKU_SCHEDULER || echo "docker-local")
-  plugn trigger scheduler-failed "$DOKKU_SCHEDULER" "$APP"
+  plugn trigger scheduler-logs-failed "$DOKKU_SCHEDULER" "$APP"
 }
 
 cmd-logs-failed "$@"

plugins/scheduler-docker-local/scheduler-logs-failed

@@ -2,9 +2,9 @@
 set -eo pipefail; [[ $DOKKU_TRACE ]] && set -x
 source "$PLUGIN_CORE_AVAILABLE_PATH/common/functions"
 
-scheduler-docker-local-scheduler-failed() {
-  declare desc="scheduler-docker-local scheduler-failed plugin trigger"
-  declare trigger="scheduler-docker-local scheduler-failed"
+scheduler-docker-local-scheduler-logs-failed() {
+  declare desc="scheduler-docker-local scheduler-logs-failed plugin trigger"
+  declare trigger="scheduler-docker-local scheduler-logs-failed"
   declare DOKKU_SCHEDULER="$1" APP="$2"
   local FAILED_CONTAINERS_FILE="${DOKKU_LIB_ROOT}/data/scheduler-docker-local/$APP/failed-containers"
   local DEAD_CONTAINERS=() DOKKU_LOGS_CMD=() RUNNING_CONTAINERS=()
@@ -53,4 +53,4 @@ scheduler-docker-local-scheduler-failed() {
   bash -c "($DOKKU_LOGS_CMD)"
 }
 
-scheduler-docker-local-scheduler-failed "$@"
+scheduler-docker-local-scheduler-logs-failed "$@"