[
https://issues.apache.org/jira/browse/COUCHDB-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901532#comment-13901532
]
Darren Gibbard commented on COUCHDB-2064:
-----------------------------------------
Just to add to this;
We make our required configuration tweaks (for example, configuring the admin
user) in local.ini; and this is centrally managed by Puppet.
Puppet in our case also auto-restarts the service when a configfile change is
detected; so the auto-addition of the UUID to local.ini causes Puppet to get
upset about it's managed config which is out of sync, corrects it, restarts
CouchDB, rinse and repeat.
One potential option would be to just push the uuid config out to
"etc/couchdb/uuid.ini" or even "etc/couchdb/local.d/uuid.ini" - ideally with a
comment section at the top briefly explaining the contents of the file so
people don't go scrapping it. Personally, i would suggest locating it outside
of "local.d" in case a user defines something like "purge" when maintaining
that directory in puppet etc.
> Move server uuid to separate file
> ---------------------------------
>
> Key: COUCHDB-2064
> URL: https://issues.apache.org/jira/browse/COUCHDB-2064
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Robert Newson
>
> Putting the uuid in local.ini causes issues for automatic provisioning
> systems.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
