plugins/plugin/subcommands/trigger

#!/usr/bin/env bash
set -eo pipefail
[[ $DOKKU_TRACE ]] && set -x

cmd-plugin-trigger() {
  declare desc="trigger an arbitrary plugin hook"
  declare cmd="plugin:trigger"
  [[ "$1" == "$cmd" ]] && shift 1

  plugn trigger "$@"
}

cmd-plugin-trigger "$@"
feat: add ability to trigger an arbitrary plugin hook This is useful in cases where the command output must be tested, but it is otherwise embedded in a specific part of the dokku core. As the 'plugin' commands require root, this is safe to add to the core. 2019-05-13 16:05:27 -04:00			`#!/usr/bin/env bash`
			`set -eo pipefail`
			`[[ $DOKKU_TRACE ]] && set -x`

refactor: standardize command naming This standardization makes it somewhat easier to read stacktraces as the command names are all uniform, so it will be slightly easier to scan trace output. 2020-02-09 22:41:39 -05:00			`cmd-plugin-trigger() {`
feat: add ability to trigger an arbitrary plugin hook This is useful in cases where the command output must be tested, but it is otherwise embedded in a specific part of the dokku core. As the 'plugin' commands require root, this is safe to add to the core. 2019-05-13 16:05:27 -04:00			`declare desc="trigger an arbitrary plugin hook"`
refactor: unify command declaration across codebase 2020-02-10 01:40:30 -05:00			`declare cmd="plugin:trigger"`
feat: add ability to trigger an arbitrary plugin hook This is useful in cases where the command output must be tested, but it is otherwise embedded in a specific part of the dokku core. As the 'plugin' commands require root, this is safe to add to the core. 2019-05-13 16:05:27 -04:00			`[[ "$1" == "$cmd" ]] && shift 1`

			`plugn trigger "$@"`
			`}`

refactor: standardize command naming This standardization makes it somewhat easier to read stacktraces as the command names are all uniform, so it will be slightly easier to scan trace output. 2020-02-09 22:41:39 -05:00			`cmd-plugin-trigger "$@"`