Brokers may return 200 for no-op update request#561
Merged
n3wscott merged 1 commit intocloudfoundry:masterfrom Jul 31, 2018
Merged
Brokers may return 200 for no-op update request#561n3wscott merged 1 commit intocloudfoundry:masterfrom
n3wscott merged 1 commit intocloudfoundry:masterfrom
Conversation
|
Hey Samze! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA. |
Contributor
|
LGTM |
1 similar comment
Contributor
|
LGTM |
mattmcneeney
approved these changes
Jul 31, 2018
n3wscott
approved these changes
Jul 31, 2018
rsampaio
added a commit
to rsampaio/servicebroker
that referenced
this pull request
Jun 9, 2020
The specification for synchronous provisioning says `201 Created` status code should be returned when for provisioning and bind and `200 OK` only for update, unbind and deprovisioning requests. This also reverts cloudfoundry#561 and assumes duplicated requests will return `409 Conflict` for the same unique UUID and it should be advised to platforms to start polling the `last_operation` endpoint to wait for completion.
This was referenced Jun 9, 2020
rsampaio
added a commit
to rsampaio/servicebroker
that referenced
this pull request
Jul 7, 2020
The specification for synchronous provisioning says `201 Created` status code should be returned when for provisioning and bind and `200 OK` only for update, unbind and deprovisioning requests. This also reverts cloudfoundry#561 and assumes duplicated requests will return `409 Conflict` for the same unique UUID and it should be advised to platforms to start polling the `last_operation` endpoint to wait for completion.
rsampaio
added a commit
to rsampaio/servicebroker
that referenced
this pull request
Oct 27, 2020
The specification for synchronous provisioning says `201 Created` status code should be returned when for provisioning and bind and `200 OK` only for update, unbind and deprovisioning requests. This also reverts cloudfoundry#561 and assumes duplicated requests will return `409 Conflict` for the same unique UUID and it should be advised to platforms to start polling the `last_operation` endpoint to wait for completion.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #539