When issuing a kill command, record which user did the kill
-
Greg Schueler- State changed from new to open
- Assigned user set to Greg Schueler
- Milestone order changed from 17 to 0
-
Greg Schueler
adding this to execution show page, as well as API execution info. Should this also be displayed within the History views?
-
Deleted UserIt make sense to have it on the history page. It's the context that's probably the most relevant to a user.
-
Greg Schueler
i'll look into it, but it might have to be punted to a refactor of the history event schema
-
Greg Schueler
proposed addition for v1 api:
<execution...>...<abortedby>username</abortedby></execution> -
Deleted User
Why aborted by? Why not killedby?
-
Greg Schueler
in the API the action is "abort" and the possible execution states include "aborted", it is not called killed.
-
Deleted User
(from [7b548d2634411cc216f5aad427af6e3a38ca470f]) Record user who performs abort/kill action for executions [#179 When issuing a kill command, record which user did the kill] https://github.com/dtolabs/rundeck/commit/7b548d2634411cc216f5aad42...
-
Greg Schueler
history log of user who performed the kill currently looks like this: http://cl.ly/323F2u3G1P3X3b2G0q0w
-
Deleted User
Looks good.
-
Greg Schueler
- State changed from open to resolved
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.