[
https://issues.apache.org/jira/browse/AURORA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146939#comment-14146939
]
Maxim Khutornenko commented on AURORA-84:
-----------------------------------------
[~wickman], we don't need Principal to display acting user in TaskEvent. We are
currently relying on security context extracted from Session object for that
[1].
[~kevints], how critical is it to have "createdBy" in the JobConfiguration? We
don't record it for regular jobs nor do we expose it anywhere for cron jobs. It
does not seem adding much auditing value either as we always have logs to track
the creator if needed.
[1] -
https://github.com/apache/incubator-aurora/blob/master/src/main/java/org/apache/aurora/scheduler/thrift/SchedulerThriftInterface.java#L829
> Deprecate the Identity struct
> -----------------------------
>
> Key: AURORA-84
> URL: https://issues.apache.org/jira/browse/AURORA-84
> Project: Aurora
> Issue Type: Task
> Components: Client, Scheduler
> Reporter: Bill Farner
> Assignee: Maxim Khutornenko
>
> The Identity field is nested in several structs, and the {{role}} field it
> contains is ~always redundant to a field in {{JobKey}}. Consider removing
> Identity and using (or adding) a non-user-bearing field like JobKey.
> An open question is whether whether {{Identity.user}} should be retained.
> Most likely yes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
