[
https://issues.apache.org/jira/browse/COUCHDB-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15550655#comment-15550655
]
ASF GitHub Bot commented on COUCHDB-3180:
-----------------------------------------
GitHub user nickva opened a pull request:
https://github.com/apache/couchdb-config/pull/14
Features API and implementation.
Implement ability to enable, disable and query feature flags.
Features are identified as binary strings. 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:feature_enable/1` : Enables a feature. Feature argument could be
a
list, a binary or an atom.
* `config:feature_disable/1` : Same as `feature_enable/1` but disables the
feature.
`feature_enable/1` and `feature_disable/1` are idempotent.
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.
Jira: COUCHDB-3180
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-config couchdb-3180
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-config/pull/14.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #14
----
commit d811a5472a91016633e217a2992df4c9ea88b876
Author: Nick Vatamaniuc <[email protected]>
Date: 2016-10-06T02:08:51Z
Features API and implementation.
Implement ability to enable, disable and query feature flags.
Features are identified as binary strings. 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:feature_enable/1` : Enables a feature. Feature argument could be
a
list, a binary or an atom.
* `config:feature_disable/1` : Same as `feature_enable/1` but disables the
feature.
`feature_enable/1` and `feature_disable/1` are idempotent.
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.
Jira: 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)
