[
https://issues.apache.org/jira/browse/MESOS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041926#comment-14041926
]
Adam B commented on MESOS-1391:
-------------------------------
FYI, repeated fields are essentially optional, since an empty list is the same
as None.
According to
https://developers.google.com/protocol-buffers/docs/proto?csw=1#updating
"optional is compatible with repeated. Given serialized data of a repeated
field as input, clients that expect this field to be optional will take the
last input value if it's a primitive type field or merge all input elements if
it's a message type field."
> Add an HTTP authentication flag which provides usernames/passwords for
> basic/digest HTTP authentication
> -------------------------------------------------------------------------------------------------------
>
> Key: MESOS-1391
> URL: https://issues.apache.org/jira/browse/MESOS-1391
> Project: Mesos
> Issue Type: Task
> Components: master, slave
> Reporter: Benjamin Hindman
> Assignee: Isabel Jimenez
>
> We'll need to authenticate HTTP endpoints for issues such as MESOS-1390. The
> first step will be determining the JSON that we should take in for describing
> the username/passwords, and possibly whether or not to capture
> "authorization" like aspects such as which endpoints users are allowed to hit
> (or assume all users are authorized for all endpoints unless a proper ACL is
> put in place).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
