Matthew Stone

I'm in favor of approach 1. IAM perms in AWS come to mind.

Noticed some strange behavior today that made me add the `to be verified` tag. On scripted install I'm seeing it operate under `stanley` user but using `id_rsa` instead of `stanley_rsa`....

See #19. I can move the logic out of the render function, but it felt right to leave it there. The implementation is complete, with example.

@dbillor we could explore the `succeeded` keyword, but the way it is now is it activates a Y[AQL function](https://github.com/StackStorm/orquesta/blob/master/orquesta/expressions/functions/workflow.py#L49). We'd need to change how those primitives get activated which isn't...

I'm not sure how I feel about `and` syntax. `and` seems like it's wanting all conditions to match to me. Could we next `next` again? Confusing?

@MichaelHills I am looking into this as well. I've noticed if you touch the screen prior to dragging in from the edges it will prevent the crash. I have put...

This also seems related to #1613 — backtrace at a glance is the same.

#1843 Resolved this on my end. Would enjoy some other 👀

It's possible to store `stdout` and `stderr` as binary data, but this wouldn't fix all cases. I'm not currently convinced ST2 should handle this case. My current view on it...

I don't immediately love the idea to be honest. If we did provide it then it would at minimum be a configurable option that defaults to requiring auth. Even then...