Remove problematic zone-endpoint-settings validation

Cannot require this, as that makes it impossible to remove a private endpoint;
the config server will attempt to create a new ZoneEndpoint with non-empty
allowed URNs, but also not a private endpoint. We could also require a two-step
decommissioning, but meh ...

1 files changed, 0 insertions, 2 deletions

diff --git a/config-provisioning/src/main/java/com/yahoo/config/provision/ZoneEndpoint.java b/config-provisioning/src/main/java/com/yahoo/config/provision/ZoneEndpoint.java
index 9f114610e32..7f54c907334 100644
--- a/config-provisioning/src/main/java/com/yahoo/config/provision/ZoneEndpoint.java
+++ b/config-provisioning/src/main/java/com/yahoo/config/provision/ZoneEndpoint.java
@@ -20,8 +20,6 @@ public class ZoneEndpoint {
     private final List<AllowedUrn> allowedUrns;
 
     public ZoneEndpoint(boolean isPublicEndpoint, boolean isPrivateEndpoint, List<AllowedUrn> allowedUrns) {
-        if ( ! allowedUrns.isEmpty() && ! isPrivateEndpoint)
-            throw new IllegalArgumentException("cannot list allowed urns, without also enabling private visibility");
         this.isPublicEndpoint = isPublicEndpoint;
         this.isPrivateEndpoint = isPrivateEndpoint;
         this.allowedUrns = List.copyOf(allowedUrns);