jaydoane edited a comment on issue #1803: Sync admin passwords at cluster setup finish URL: https://github.com/apache/couchdb/pull/1803#issuecomment-449662756 @wohali I would be down with working on the docs, but I'm not sure which route to take. Do we really want to document both scenarios, when it seems like (especially after this patch) there's no obvious upside to using one over the other? It also occurs to me that, since one can now set up a cluster by making multiple requests to a single coordinator node, the whole process could in principle be made much simpler by changing the setup code to support a _single_ request to the coordinator with all the information necessary in one data structure. For example, we could in principle deprecate the entire series of error-prone and confusing requests with something like this: ``` POST /_cluster_setup { "nodes": [ { "url": "http://user2:[email protected]:25984";, "name": "node2" }, { "url": "http://user3:[email protected]:35984";, "name": "node3" } ], "admins": [ "adm:pass" ] } ``` where "nodes" represents an optional list of additional nodes in the cluster, and "admins" is an optional (?) list of all admins to be configured. A "node" object could also include an optional "bind_address", and perhaps other useful fields. This would also allow for (possibly randomly generated) individual creds for each node prior to forming a cluster. The POST request itself implicitly requires the credentials "user1:pass1" to authenticate. I think I'll play around with prototyping this unless you think it's a terrible idea for some reason.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
