shc notification emit
shc notification emit
Section titled “shc notification emit”raise a coded event through every matching notification rule
Synopsis
Section titled “Synopsis”Raise a coded event through every notification rule whose on matches its code, as the daemon’s own events are raised. Each rule’s cooldown and debounce apply: a rule that sent this code inside its cooldown sends nothing, and one with a debounce window holds the event to send with the others the window collects. Prints what each matching rule did. Use shc notification test to send through one rule now, bypassing both.
shc notification emit [flags]Options
Section titled “Options” --code string event code to raise, matched against each rule's on patterns -h, --help help for emit --message string event message --payload string JSON payload to attach to the eventOptions inherited from parent commands
Section titled “Options inherited from parent commands” --config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win -d, --debug enable debug mode (default: $SHC_DEBUG) -e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default") --exclude string comma-separated dotted paths to drop --fields string comma-separated columns/keys to show (and their order) --filter string comma-separated dotted paths to keep (drops everything else) -o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT) -s, --stack string stack name (default: $SHC_STACK) -t, --tenant string tenant name (default: $SHC_TENANT) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc notification - list, test and emit through notification routing rules
shc@docs:~$