-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mixed case Plans #422
Comments
@mattmcneeney @zrob can you guys confirm that CF allows uppercase letters in Plan names? |
on today's call we tentatively agreed to change the spec to allow uppercase letters. PR coming soon. |
CF allows both plan names and service names to have mixed case, so it would be great to update the spec. to loosen the requirements on both of these fields. Interesting side note: When checking for unique service names and broker registration time, CF doesn't allow for two services to be registered regardless of case, i.e. "test" and "TEST". But it is possible to register a service called "MyService". |
Closes openservicebrokerapi#422 Signed-off-by: Doug Davis <dug@us.ibm.com>
Closes openservicebrokerapi#422 Signed-off-by: Doug Davis <dug@us.ibm.com>
Closes openservicebrokerapi#422 Signed-off-by: Doug Davis <dug@us.ibm.com>
Right now the spec requires that plan names be all lowercase letters, however CF allows mixed-case letters. While we could look at this as bug in CF, since CF is the baseline implementation on which the spec is based (and we don't want to break existing brokers), I'm wondering if we need to loosen the language in the spec or ask CF to be spec compliant. I'm leaning towards changing the spec.
The text was updated successfully, but these errors were encountered: