From d30a948be03873694070753e25e5be52cb4a2962 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Sun, 12 May 2019 05:15:53 -0400 Subject: [PATCH] feat: silence dokku run 'errors' In certain cases, a command can be specified but found - or not - in the Procfile, resulting in unnecessary output for cron tasks. Closes #3522 --- plugins/scheduler-docker-local/scheduler-run | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plugins/scheduler-docker-local/scheduler-run b/plugins/scheduler-docker-local/scheduler-run index 0b3a228ff..22a374204 100755 --- a/plugins/scheduler-docker-local/scheduler-run +++ b/plugins/scheduler-docker-local/scheduler-run @@ -47,11 +47,11 @@ scheduler-docker-local-scheduler-run() { DOKKU_QUIET_OUTPUT=1 extract_procfile "$APP" POTENTIAL_PROCFILE_KEY="$1" - PROC_CMD=$(get_cmd_from_procfile "$APP" "$POTENTIAL_PROCFILE_KEY" || echo '') + PROC_CMD=$(get_cmd_from_procfile "$APP" "$POTENTIAL_PROCFILE_KEY" 2>/dev/null || echo '') remove_procfile "$APP" if [[ -n "$PROC_CMD" ]]; then - dokku_log_info1 "Found '$POTENTIAL_PROCFILE_KEY' in Procfile, running that command" + dokku_log_info1_quiet "Found '$POTENTIAL_PROCFILE_KEY' in Procfile, running that command" set -- "$PROC_CMD" "${@:2}" fi