diff options
author | Håkon Hallingstad <hakon@verizonmedia.com> | 2019-10-22 00:28:22 +0200 |
---|---|---|
committer | Håkon Hallingstad <hakon@verizonmedia.com> | 2019-10-22 00:28:22 +0200 |
commit | c29b374c582c8b112a6e95150e5d4a460dc30464 (patch) | |
tree | a9ec0e5bb3a388d6c30199bd3b89b07b1bcb716e /flags/pom.xml | |
parent | fef3449937c173ef8128b6085829e0bbe3f97ce4 (diff) |
Support flag conditions based on Vespa release
Supports a "relational" condition with a new dimension "vespa-version", that
can be satisfied with e.g. "predicate": ">= 7.120.5" as long as the condition is
evaluated in a JVM that has a Vtag at least high as 7.120.5.
The typical use-case for this condition would be: The developer has used the
flag to test and verify the feature is ready to roll out globally. The
developer can now roll the feature with the next release, and ORCHESTRATED,
halting if anything goes wrong like any normal rollout.
This also allows one-shot tests of a feature flag in integration tests: Just
enable it for an upcoming version with predicate "== 7.x.y".
Diffstat (limited to 'flags/pom.xml')
-rw-r--r-- | flags/pom.xml | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/flags/pom.xml b/flags/pom.xml index c1e9eca20ab..6afa920e261 100644 --- a/flags/pom.xml +++ b/flags/pom.xml @@ -27,6 +27,12 @@ </dependency> <dependency> <groupId>com.yahoo.vespa</groupId> + <artifactId>component</artifactId> + <version>${project.version}</version> + <scope>provided</scope> + </dependency> + <dependency> + <groupId>com.yahoo.vespa</groupId> <artifactId>defaults</artifactId> <version>${project.version}</version> <scope>provided</scope> |