Skip to content
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

Incompatible change in v2.12: the broker MUST return 200 OK if the binding already exists #528

Closed
fmui opened this issue Jun 13, 2018 · 2 comments
Assignees

Comments

@fmui
Copy link
Member

fmui commented Jun 13, 2018

In the v2.11 spec, the broker had a choice to return 200 OK when the platform sends identical parameters for an exiting binding.
The expected broker behavior changed in v2.12 to a MUST.

v2.11:

200 OK May be returned if the binding already exists and the requested parameters are identical to the existing binding.

v2.12:

200 OK MUST be returned if the binding already exists and the requested parameters are identical to the existing binding.

Although v2.11 was ambiguous, we are now in a situation where v2.11 brokers may not work with platform supporting v2.12 or v2.13.

@mattmcneeney mattmcneeney self-assigned this Jun 19, 2018
fmui added a commit to fmui/servicebroker that referenced this issue Jul 4, 2018
@fmui
Copy link
Member Author

fmui commented Jul 4, 2018

See PR #540 .

@duglin
Copy link
Contributor

duglin commented Jul 17, 2018

Closing since #540 is closed/merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants