[
https://issues.apache.org/jira/browse/COUCHDB-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654444#comment-15654444
]
ASF subversion and git services commented on COUCHDB-3180:
----------------------------------------------------------
Commit f62d553b337ce975edb0fb68772d22bdd3bf6490 in couchdb-config's branch
refs/heads/master from [~vatamane]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-config.git;h=f62d553 ]
Features API and implementation.
Implement ability to enable, disable and query feature flags.
Features are identified as atoms. Usage intent is for various components in the
system to enable features, then the HTTP API will expose those to the user.
For example, features could indicate the presence of an optional component, a
plugin or a new mode of operation.
The API has 3 functions:
* `config:features/0` : Return a sorted list of feature flags
* `config:enable_feature/1` : Enables a feature. Feature argument could be a
list, a binary or an atom.
* `config:disable_feature/1` : Disables a feature.
Implementation is a thin wrapper around setting and deleting keys from the
'[features]' config section. This means, users can also set their own features
there via the .ini config files. Features set via the API are not persistent,
so applications will have to set them every time they initialize.
COUCHDB-3180
> Add ability to return a list of features in server's welcome message
> --------------------------------------------------------------------
>
> Key: COUCHDB-3180
> URL: https://issues.apache.org/jira/browse/COUCHDB-3180
> Project: CouchDB
> Issue Type: New Feature
> Reporter: Nick Vatamaniuc
>
> This could be used to let users discover quickly the availability of some API
> or modes of operation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
