Plugins

cat > ~/.local/bin/bronto-errors <<'EOF'
#!/bin/sh
# bronto errors <dataset>: last hour of 5xx responses as a table
exec bronto search "status >= 500" -d "$1" --since 1h -o table
EOF
chmod +x ~/.local/bin/bronto-errors

bronto errors prod/checkout-service   # runs the plugin (skilldoc:ignore: not a built-in)

​

How dispatch works

• The plugin name must be the first argument. bronto errors --help runs the plugin with --help. bronto --profile prod errors does not dispatch, because a flag comes first. Put global flags after the plugin name and let the plugin handle them.
• Built-in commands always win. A bronto-search executable can’t replace bronto search.
• Names are restricted to lowercase letters, digits, and dashes.
• If several directories on PATH contain the same plugin, the first one wins, as with any command lookup.
• The plugin’s exit code becomes bronto’s exit code, and its output passes through untouched.

$ bronto plugins list

​

Credentials for plugins

• Call bronto itself, as the example above does. The nested call resolves credentials the normal way.
• Ask for the key with bronto auth token, which prints the key the CLI would use:
  BRONTO_API_KEY="${BRONTO_API_KEY:-$(bronto auth token)}"