summaryrefslogtreecommitdiff
path: root/puppet/modules/couchdb
AgeCommit message (Collapse)Author
2015-11-25added submodule couchdbvarac
2015-11-17[feat] updated submodules to work with jessievarac
- sshd - couchdb - apache - Related: #6920
2015-10-17[bug] updated submodule couchdbvarac
- Tested: [local singlenode, citest] - Resolves: #7530
2015-10-17switch to ensure_packages to avoid puppet duplicate package definitions (#7530)Micah
Change-Id: I398b929fc96cf64e46075266ace0d8d1145b3aac
2015-10-13updated submodule couchdbvarac
2015-10-08Update submodule couchdbvarac
2015-06-29updated submodule couchdb to remove debugging leftover notice()varac
Change-Id: I9c901a21c2ae3cd0164ca9bd3b4aab63d6a239c7
2015-06-11updated submodule couchdbvarac
Change-Id: Id5bc16d8466c3407e9f7c4015c1e3a96129daf0a
2015-06-11updated submodule couchdb (Couchdb >=1.3 uses pbkdf2 as pw hashing ↵varac
algorhythm, #7120) Change-Id: I97560f4134a700579d1523ddd8ba173bfb1f0659
2015-05-14use latest puppet_couchdbelijah
2015-04-26update couchdb submoduleelijah
2015-02-03update couch-doc-update to catch a more specific exception (#6699)Micah Anderson
Change-Id: I4f7a13443574d5771ebd9dd2278ef64ba8593a7a
2015-01-13update couchdb submodule to get fix for #6287Micah Anderson
Change-Id: I2ad21d93580d2ba373cde7c4de4d32bd281e06ca
2014-11-04change ordering hints to use refresh_stunnel exec instead of service (#6287)Micah Anderson
In a multi-node couch deployment, it was observed that the Service['stunnel'] would be activated, and then later a stunnel::client was created which would trigger an Exec['refresh_stunnel']. Because of this, and the ordering hints that were in place, the service would get started, and then the couchdb databases, users, designs, etc. were being put into place and then a stunnel client was created, triggering the refresh_stunnel exec, which would cause an interruption in the connectivity and result in failures. This change replaces the Service['stunnel'] hint with the the Exec['refresh_stunnel'] to make sure that the stunnels are fully setup before attempting couch operations. Change-Id: I33ddd24884b3c23a1df5555ca53ca65cd703da50
2014-07-14update couchdb puppet moduleAzul
2014-06-25update couchdb submoduleelijah
2014-04-17update couchdb submodule to get fix for timing issue that caused 409 ↵0.5.0Micah Anderson
Conflicts in certain situations (#5523) Change-Id: I1ca67e317a7eb84f64cb7b79daa2e500f0561707
2014-01-21updated submodule couchdbvarac
2014-01-04updated submodule couchdbvarac
2013-12-17updated submodule couchdbvarac
2013-12-17replace couch-doc-update with one that uses MultiJson instead, this could ↵Micah Anderson
prevent the outdated json errors (#4622) Change-Id: Ibd929045a28eef1e9262fad8953df8fd150c1966
2013-12-17update couchdb::add_user to use couchdb::document (#4624)Micah Anderson
Change-Id: Ie7810d7e851f5023bc8970cccc888eccb8661856
2013-11-27enable uploading a document to couch from a file (#4256)Micah Anderson
deploy design documents during couch deploy (#3771) Change-Id: I4679e066303ac9b02582214c48e2e7dcfe5bd651
2013-11-25add new version of couchdb submodule0.3.0rc4Azul
This one reverts a buggy fix. Trying to push it out asap
2013-11-22update couchdb submodule to get debugging output #4225Micah Anderson
Change-Id: Ie1b6d67f493ed6891a2df76b044d64d359edb420
2013-10-30Users with access to a db are called members - not readers (#4219)Azul
( they can read and write ). I think couch themselves changed the termology at some point but i might just have used the wrong term from the beginning on. Let's call them members either way because it's more clear that read only members require aditional design docs.
2013-10-16updated submodule couchdbvarac
2013-09-25recent couchdb puppet - requires git submodule updateAzul
2013-09-04updated couchdb submodule: bigcouch nodes doesn't get registered as cluster ↵varac
members (Bug #3703)
2013-09-04updated submodule couchdb: don't use couchdb::document for creating ↵varac
_security, cause this special doc doesn't have and _id (#3706)
2013-08-30updated submodule couchdb: couchdb: update_user_webapp fails (Bug #3611)varac
2013-08-29updated submodule couchdb, fixed merge resolution error from last mergevarac
2013-08-29updated submodule couchdb, fix puppet couchdb module doesn't create ↵varac
necessary databases anymore (Bug #3594)
2013-08-27updated submodule couchdbvarac
2013-08-27updated submodule couchdbvarac
2013-08-21update couchdb module to resolve #3459Micah Anderson
Change-Id: Icad17de812392d7c587e5bcbf60cd5242c1241e9
2013-08-16update couchdb submodule to fix #3481Micah Anderson
Change-Id: I474cc691fcfc892b7aff4a3a0e3954155bf5ee30
2013-08-14update couchdb submodule to the latest version - fixes #3447Micah Anderson
Change-Id: Ib6458b962c624fdb75f514dbd4c2129581fc2bb7
2013-05-23update couchdb submodule to get couchdb::bigcouch::add_node and ↵Micah Anderson
couchdb::bigcouch::query
2013-04-24automatic update of submodule couchdbvarac
2013-04-24automatic update of submodule couchdbvarac
2013-04-23automatic update of submodule couchdbvarac
2013-04-04update submodule to get fix for syntax errorMicah Anderson
2013-04-04add Erlang Distributed Node Protocol Port json entry under bigcouchMicah Anderson
setup ednp_server and ednp_client stunnels update couchdb puppet submodule to support configurable ednp_port parameter and general module cleanup pass ednp_port to couchdb setup so that it is configured in the vm.args template clarify in comments the difference between the epmd and ednp ports remove hard-coded erlang_vm_port variable and instead setup shorewall to allow for the stunnel connection only setup dnat rules for the ednp client connections
2013-03-31automatic update of submodule couchdbMicah Anderson
2013-03-15automatic update of submodule couchdbvarac
2013-03-15automatic update of submodule couchdbvarac
2013-03-14automatic update of submodule couchdbvarac
2013-03-13automatic update of submodule couchdbvarac
2013-03-13automatic update of submodule couchdbvarac