Cog is a sophisticated chatbot featuring command pipes for Unix-style commands.
At this time a fairly comprehensive guide to installing on Kubernetes on AWS is located here.
Relays are how Cog actually performs various functions. Commands are sent down to be executed by the relays and in most cases you will want a relay also on the Cog master or in the same cluster as one.
Relays are also required to be installed via interactive command line on the master with cogctl. This seems to be for security reasons.
A user is an account created within Cog that can be associated by is not required to be with the actual chat interface. Direct user creation can only be performed via interactive command line on the master with cogctl. This seems to be for security reasons.
Most commands are formed from Command Bundles. While specifying the command in [bundle]:[command] format is not required it helps with disambiguation in case multiple bundles provide commands of the same name. For this reason in this section they will be listed in this format.
Get help for a command bundle:help [bundle]
Get help for a command:help [bundle]:[command]
Command Bundles can be directly managed from the Cog master instance with cogctl.
Creation: from the chat use the operable command bundle to create a trigger. Talking to your bot, issue commands in the form of:
trigger-create [trigger name] [pipeline command] [options]
Example triggers are as follows:
trigger-create echo-test 'echo "Hi there, " $host ", says it needs your help." > chat://@slackuser' -d "Get admin's attention when a system is down" -u cogbotusertrigger-create thing-happened-somewhere 'echo "Uh oh, something is down in " $body.location "!" > chat://#slackchannel' -d "Alert users in a channel from JSON" -u cogbotuser
Invocation: triggers are intended primarily to be called by API REST call. If variables are required while it supports several methods it's recommended to use JSON variables if possible. An example is as follows: