summaryrefslogtreecommitdiffstats
path: root/orchestrator-restapi/pom.xml
diff options
context:
space:
mode:
authorHåkon Hallingstad <hakon@yahoo-inc.com>2017-06-12 01:13:05 +0200
committerHåkon Hallingstad <hakon@yahoo-inc.com>2017-06-12 01:13:05 +0200
commit29f331a02b091d1dbd958a95c8b562165326d76a (patch)
tree37f3cff32b20137af09f131d80f5fecea2e6b945 /orchestrator-restapi/pom.xml
parent3d0f44f63919702713908b8da56434a5260f18df (diff)
Orchestrator support for setting host status
Directly setting the host status can be useful for an operator, e.g. to break a deadlock. Unfortunately, some code use the term "host status" while others use "host state". I haven't settled yet on which is preferred, e.g. 'state' is used in REST APIs, but 'status' is the original term and slightly more used. This PR maintains the local use of the terms, meaning it adds 'state' where that's normally used and 'status' other places. Setting the deadlock is done with a PATCH request, which is defined in jaxrs_utils. jaxrs_utils only defines PATCH, and that's not used anywhere else except in jaxrs_client_utils tests. So I remove this module as a dependency a couple of places.
Diffstat (limited to 'orchestrator-restapi/pom.xml')
-rw-r--r--orchestrator-restapi/pom.xml6
1 files changed, 6 insertions, 0 deletions
diff --git a/orchestrator-restapi/pom.xml b/orchestrator-restapi/pom.xml
index b2b581a7fc6..79e8dc3e618 100644
--- a/orchestrator-restapi/pom.xml
+++ b/orchestrator-restapi/pom.xml
@@ -22,6 +22,12 @@
<scope>provided</scope>
</dependency>
<dependency>
+ <groupId>com.yahoo.vespa</groupId>
+ <artifactId>jaxrs_utils</artifactId>
+ <version>${project.version}</version>
+ <scope>compile</scope>
+ </dependency>
+ <dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-annotations</artifactId>
<version>${jackson2.version}</version>