[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7973 at 7/12/17 9:17 AM: -------------------------------------------------------------------- Things to clarify and other issues: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). * Shall we create separate separate service or one service with multiple plans? * It seems there is no way to let the client specify how the secret created by binding should look like. It can be defined from a service broker perspective (have a look at this [test|https://github.com/openshift/origin/blob/f4b675ea183f1ebec3d15373337...]). So it might be better (for now?) to let the template create a secret for Service Consumers. * In addition to previous point - it seems that [MariaDB Template|https://github.com/openshift/origin/blob/master/examples/db-temp...] handles this correctly. We should copy its behavior. was (Author: sebastian.laskawiec): Things to clarify and other issues: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). * Shall we create separate separate service or one service with multiple plans? * It seems there is no way to let the client specify how the secret created by binding should look like. It can be defined from a service broker perspective (have a look at this [test|https://github.com/openshift/origin/blob/f4b675ea183f1ebec3d15373337...]). So it might be better (for now?) to let the template create a secret for Service Consumers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)