Age | Commit message (Collapse) | Author |
|
|
|
couch db readers actually are couchdb members ( 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.
|
|
|
|
|
|
|
|
special doc doesn't have an _id (#3706)"
This reverts commit dacaeb4d98be9468336923f5501822d389bda768.
couch-doc-update and thus couchdb::document now also work for _security
documents. We simply add the given _id when none is present in the
existing doc. Using the normal saving of CouchRest::Document then works.
|
|
It also clears doc fields that are not set in the new data when updating a doc.
|
|
curl -f will fail if a 400 or 500 response code is returned
|
|
Both the couch document and the second paramter will be pretty printed
before comparison so differences in spaces etc. do not matter.
All keys starting with an underscore on the couch such as _id and _rev
will be removed before the comparison - we assume we want to compare
the real data, not the metadata about the document as we usually do not
know or care about what the id and revision will be.
|
|
|
|
|
|
|
|
|
|
|
|
doesn't have and _id (#3706)
|
|
|
|
|
|
Conflicts:
manifests/create_db.pp
|
|
|
|
|
|
fixes the use of couch-doc-update with non standart hosts
replaces couchdb::bigcouch::query with couchdb::bigcouch::document
|
|
also made the use of host, hostname and port a bit more consistent.
|
|
Added the bash script couch-doc-diff.
It runs a diff between the content of the couch document specified as the first parameter and the second parameter.
Diff returns 0 if there is no difference. This way you can tell the data is already on the couch.
The diff will ignore changes to whitespaces as these are usually irrelevant for security json docs.
|
|
|
|
fixes https://leap.se/code/issues/3527
|
|
|
|
python-couchdb), and we cannot depend on those external resources. Because we setup a symlink to /etc/couchdb when the couchdb package gets installed it will try to write files there and will fail with the an error similar to the following:
/Stage[main]/Couchdb::Base/File[/etc/couchdb/local.ini]/ensure: change from absent to file failed: Could not set 'file on ensure: No such file or directory - /etc/couchdb/local.ini.puppettmp_9420 at /srv/leap/puppet/modules/couchdb/manifests/base.pp:57
this change just manages the /etc/couchdb directory to make sure it exists before anything attempts to install there
|
|
|
|
|
|
|
|
We test the user account by trying to use it to retrieve / on the couch which prints a welcome message if the user is valid and returns a 401 otherwise.
|
|
manage /etc/couchdb, having a file resource that creates a symlink out of /etc/couchdb doesn't work, for example you can get this error:
err: /Stage[main]/Couchdb::Bigcouch/File[/etc/couchdb]/ensure: change from directory to link failed: Could not remove existing file (Bug #3447)
This commit resolves this by instead managing /opt/bigcouch (as this is where the bigcouch package is installed) and creating a symlink *from* /opt/bigcouch/etc -> /etc/couchdb before the bigcouch package is installed. This way, when the package is installed, the files will be placed in the /etc/couchdb directory and other packages that would create/manage /etc/couchdb would not get confused.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
see http://stackoverflow.com/questions/8459949/bigcouch-cluster-connection-issue#comment10467603_8463814
|
|
|
|
|
|
|
|
|
|
|
|
So Couchdb::Query and Couchdb::Update doesn't try to connect
to couchdb before it is up and running. That fixes a nasty race
condition, see Fix doc update error on puppetrun (Feature #1964).
|