gort
gort copied to clipboard
getgort
Gort is a chatbot framework designed from the ground up for chatops.
The parsing functionality provided by the `command` and `types` packages currently has several major limitations that should be addressed: - [ ] Repeated flags (ex. `-vvv` for verbosity level) are...
Currently (after #226 merges) the scheduler has very naive permissions, allowing anyone to schedule any command that they are able to call directly, and anyone to delete any command. A...
Ideally, the scheduler should not create multiple schedules with the same adapter, channel, command, and cron string, making the schedule create endpoint idempotent. It may be possible that we want...
Cog had a really nifty feature that allowed privileged users to create custom API endpoints -- additions to the Cog REST API -- that could be used to trigger commands...
Currently, command output is limited to plain text, as if it was any command line tool. This is adequate for simple use cases, but doesn't allow for the addition of...
Currently Gort only responds to explicit commands, formatted like structured commands. There should be some kind of ability to respond to non-command text, sort of like Slack "triggers" (but not...
Just found gort and looks very interesting. As I'm looking for using Matrix for my purposes, I could not find any support, which is understandable. However, I've seen in the...
Long outputs (such as the help message from `kubectl`) don't generated reasonable output. * Slack: A `invalid_blocks` appears, followed by the text in plain (not monospace) format * Discord: An...
Commands often require access to runtime variables, particularly when interacting with external services, ranging from mundane values (like the URL of a downstream resource) to highly sensitive information (like database...
Currently audit logs are written to the database, but access to them requires querying the table directly. A `gort logs` command would be very helpful. * It should only be...