[Feature] Return TaskID when executing a run-runbook Command

[MattHodge]

Hi There,

Is it possible to return the TaskID of the task that was created by executing the octo run-runbook command as part of the json output here?

The use case is I want to trigger a Runbook via the API, and then go and grab any artifacts attached like in the documentation example, but without having to do the lookup.

Thanks!

[MattHodge]

It looks like this information is available in the logs when using the --debug flag:

The request is to return the ServerTaskId (in this example, ServerTasks-133285) as part of the JSON result.