aboutsummaryrefslogtreecommitdiffstats
path: root/configserver-flags/pom.xml
Commit message (Collapse)AuthorAgeFilesLines
* Update copyrightJon Bratseth2023-10-091-1/+1
|
* Use Guice 6.0Bjørn Christian Seime2023-09-041-1/+1
| | | | | | https://github.com/google/guice/wiki/Guice600 We cannot upgrade to 7.x as we export javax.inject from container. 6.x supports both the old javax.inject and the new jakarta.inject replacement.
* - Update dependency org.jvnet.mimepull:mimepull to v1.10.0renovate[bot]2023-08-291-5/+0
| | | | | | | | - Update dependency org.apache.opennlp:opennlp-tools to v1.9.4 - Use dependency-versions - Bring jimfs up to date. - Bring some more libraries up-2-date. - Reduce usage of assertj
* Consolidate hamcrest usage to 2.x and remove cthul-matchersBjørn Christian Seime2023-08-291-5/+1
|
* Convert configserver-flags to junit5Bjørn Christian Seime2022-07-281-4/+29
| | | | Replace use of Hamcrest with junit5/assertj assertions
* Remove all dependencies to yoleangjoranv2022-07-131-6/+0
|
* Remove temporary dependency on 'jetty-http' with test scopeBjørn Christian Seime2022-06-081-7/+6
|
* Set project version to 8-SNAPSHOTgjoranv2022-06-081-2/+2
|
* Don't provide Jetty bundles from 'container' artifactBjørn Christian Seime2022-06-081-0/+7
| | | | Add dependency on 'jetty-http' with scope test instead of adding false dependencies with 'container-test'.
* Update 2017 copyright notices.gjoranv2021-10-071-1/+1
|
* Decouple flags REST API from config serverMartin Polden2019-07-161-0/+6
|
* Read override file flags from file only once for config serverHåkon Hallingstad2019-01-261-0/+6
| | | | | | | | | | | | | | | | | | Up until now, every lookup of a flag in the ConfigServerFlagSource would 1. try to read 2 flag files under /etc/vespa/flags, causing exceptions because they are typically not set, and 2. then read flag from ZooKeeper through ZooKeeperFlagSource Optimization was deliberately held off until later (now). This PR fixes (1). Changes the ConfigServerFlagSource to: 1'. Read VESPA_HOME/var/vespa/flag.db once during component graph construction. As before, if a flag is defined on file, the flag is not looked up in ZK, which may be useful in emergencies. 2. As before. Also, removes the last usages of FileFlagSource and its reading of flags in /etc/vespa/flags.
* Set 7-SNAPSHOT for new module, and remove redundant 'name'.gjoranv2019-01-211-3/+2
|
* Configserver flags REST APIHåkon Hallingstad2018-12-301-0/+100
Adds a new ZooKeeper backed flag source. It is defined in a new module configserver-flags to allow as many as possible config server modules to depend on it by minimizing dependencies. The content of the ZK backed flag source can be viewed and modified through REST API on the config server/controller. The data stored per flag looks like { "rules": [ { "conditions": [ { "type": "whitelist", "dimension": "hostname", "values": ["host1"] } ], "value": true } ] } typical for enabling a feature flag on host1. 2 types of conditions are so far supported: whitelist and blacklist. All the conditions must match in order for the value to apply. If the value is null (or absent), the default value will be used. At the time the flag's value is retrieved, it is resolved against the conditions with the current zone, hostname, and/or application. The same data structure is used for FileFlagSource for files in /etc/vespa/flags with the ".2" extension. The FlagSource component injected in the config server is changed to: 1. Return the flag value if specified in /etc/vespa/flags, or otherwise 2. return flag value from ZooKeeper (same as REST API) The current flags (module) is also changed: - All flags must be defined in com.yahoo.vespa.flags.Flags. This allows the ZK backed flag source additional sanity checking when modifying flags. - If it makes sense to have different flag value depending on e.g. the application, then at some point before the value is retrieved, one has to bind the flag to that application (using with() to set up the fetch vector). Future changes would be to 0. make a merged FlagSource in host admin, 1. add support for viewing and modifying feature flags in dashboard, 2. in hv tool.