tommikarkkainen opened a new pull request #630:
URL: https://github.com/apache/couchdb-documentation/pull/630
<!-- Thank you for your contribution!
Please file this form by replacing the Markdown comments
with your text. If a section needs no action - remove it.
Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
of code collaboration. Positive feedback is represented +1 from
committers
and negative is a -1. The -1 also means veto, and needs to be addressed
to proceed. Once there are no objections, the PR can be merged by a
CouchDB committer.
See: http://couchdb.apache.org/bylaws.html#decisions for more info. -->
## Overview
CouchDB 3.0 no longer allows users to access or modify documents in the
`_users` database. This PR changes the Introduction documents to reflect those
changes.
- I kept the existing information on 2.0 behaviour (users can access their
own documents) but mentioned that it needs a change in settings, and will not
be possible in 4.0. This is mentioned in a note so that it is easy to remove
for 4.0.
- I removed the Users Public Information section which seems to revolve
around a use case where users access documents in `_users`. This change is in a
separate commit so it can be easily undone if deemed necessary.
- #513 mentions mandatory fields, but as far as I can tell the documentation
on that is not strictly incorrect. The fields related to passwords and salts
are generated automatically, and when I tried I couldn't create a user without
the roles field. If changes to documentation are needed in this regard, I don't
have enough knowledge on the inner workings of CouchDB to make those.
<!-- Please give a short brief for the pull request,
what problem it solves or how it makes things better. -->
## Testing recommendations
<!-- Describe how we can test your changes.
Does it provides any behaviour that the end users
could notice? -->
## GitHub issue number
#513
<!-- If this is a significant change, please file a separate issue at:
https://github.com/apache/couchdb-documentation/issues
and include the number here and in commit message(s) using
syntax like "Fixes #472" or "Fixes apache/couchdb#472". -->
## Related Pull Requests
<!-- If your changes affects multiple components in different
repositories please put links to those pull requests here. -->
## Checklist
- [ ] Update
[rebar.config.script](https://github.com/apache/couchdb/blob/main/rebar.config.script)
with the commit hash once this PR is rebased and merged
<!-- Before opening the PR, consider running `make check` locally for a
faster turnaround time -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
