Use new restapi handler implementation by default

Remove feature flag for enabling the new handler.
Cleanup wiring of old and new handler in model.

1 files changed, 0 insertions, 7 deletions

diff --git a/flags/src/main/java/com/yahoo/vespa/flags/Flags.java b/flags/src/main/java/com/yahoo/vespa/flags/Flags.java
index bf3b497bc3f..ab12558bec7 100644
--- a/flags/src/main/java/com/yahoo/vespa/flags/Flags.java
+++ b/flags/src/main/java/com/yahoo/vespa/flags/Flags.java
@@ -6,7 +6,6 @@ import com.yahoo.vespa.defaults.Defaults;
 import com.yahoo.vespa.flags.custom.HostCapacity;
 import com.yahoo.vespa.flags.custom.SharedHost;
 
-import java.math.BigDecimal;
 import java.util.List;
 import java.util.Optional;
 import java.util.TreeMap;
@@ -303,12 +302,6 @@ public class Flags {
             "Takes effect at next run of maintainer",
             APPLICATION_ID);
 
-    public static final UnboundBooleanFlag USE_NEW_RESTAPI_HANDLER = defineFeatureFlag(
-            "use-new-restapi-handler",
-            false,
-            "Whether application containers should use the new restapi handler implementation",
-            "Takes effect on next internal redeployment");
-
     public static final UnboundBooleanFlag USE_ACCESS_CONTROL_CLIENT_AUTHENTICATION = defineFeatureFlag(
             "use-access-control-client-authentication",
             false,