15a2b7cbce
Often-times, we will want to have the container inspect output for debugging purposes, but this process is: - error prone, as the user needs to know what their containers are - potentially insecure, as the output must be sanitized of sensitive data Instead of making users wade through this process, we provide a helper `ps:inspect` command, that can be used to diagnose problems associated with containers that may or may not exist for an application.
6 lines
142 B
Bash
Executable File
6 lines
142 B
Bash
Executable File
#!/usr/bin/env bash
|
|
source "$PLUGIN_AVAILABLE_PATH/ps/internal-functions"
|
|
set -eo pipefail; [[ $DOKKU_TRACE ]] && set -x
|
|
|
|
cmd-ps-inspect "$@"
|