Christopher Maier
Christopher Maier
HipChat integration tests appear to be failing in Travis CI. The following is representative of the failing output. ``` ** (MatchError) no match of right hand side value: {:error, {%RuntimeError{message:...
Currently when Cog finishes a pipeline stage and there is no output to pass to downstream stages, a message is output saying ["Pipeline executed successfully, but no output was returned"](https://github.com/operable/cog/blob/1229b19a22f217273ed6617c114d0055f3aff0ec/priv/templates/common/early-exit.greenbar)....
It appears that Piper isn't enforcing the declared types of option values, causing commands to manage this on their own. If we could be certain that the data we receive...
Provide per invocation / pipeline log viewing (e.g., what data came into this command, what went out of it). Once we can send multiple outputs from a pipeline, this would...
We need to clearly lay out the usecases we want to serve with errors and aborts, as the distinction between them currently is a little muddy. Currently, a command can...
Ideally, something that we can execute independently of the executor. This would make testing return values a lot easier, at the very least, as they wouldn't be filtered through the...
Commands that are expected to take a long time to run (e.g., synchronous creation of infrastructure) can fail with Cog simply because they exceed the built-in timeout for a command....
Commands executing in the context of a trigger invocation can currently access user-layer dynamic configuration (user specified in trigger definition or through request headers), but cannot access room-layer dynamic configuration....
Provide a means to set global data for a pipeline (e.g. `"with --region=us-east-1 | ec2:list ... | ec2:terminate"` This would involve having nested scopes in Piper, as well as a...
The `operable:role` chat command prevents deletion of the role if it is granted to any users or groups. This functionality exists only in the chat command, and not in the...