Allow users to edit route TLS if they can create custom hosts

Author: spadgett

Diff for: app/scripts/directives/oscRouting.js

@@ -75,7 +75,10 @@ angular.module("openshiftConsole")
 
         // Certificate updates also require custom host.
         scope.areCertificateInputsReadOnly = function() {
-          return !canISetCustomHost();
+          // For both new and existing routes, you can update TLS if you can
+          // *create* custom hosts.
+          // See https://github.com/openshift/origin/pull/18312
+          return !scope.canICreateCustomHosts;
         };
 
         scope.areCertificateInputsDisabled = function() {

Diff for: dist/scripts/scripts.js

@@ -10056,7 +10056,7 @@ return r.existingRoute ? r.canIUpdateCustomHosts : r.canICreateCustomHosts;
 r.isHostnameReadOnly = function() {
 return !c();
 }, r.disableWildcards = t.DISABLE_WILDCARD_ROUTES, r.areCertificateInputsReadOnly = function() {
-return !c();
+return !r.canICreateCustomHosts;
 }, r.areCertificateInputsDisabled = function() {
 var e = _.get(r, "route.tls.termination");
 return !e || "passthrough" === e;