Skip to content

Conversation

@gberche-orange
Copy link
Member

Incomplete POC aiming to replace V2 api calls with V3 for service bindings following #231

  • Failed to replace v2 operations call with v3 low level clients while preserving synchronous service binding OSB user-experience, and reactive programming model. Reverted to using imperative blocking calls
  • Still using v2 operations for space and service instances

fix #44

…hen broker returns sync response.

As a result, the CreateDeleteAsyncInstanceWithSyncBackingServiceKeysAcceptanceTest fails with error Service broker error: backing osb-cmdb broker requires async

Corresponding code base:
https://github.com/cloudfoundry/cloud_controller_ng/blob/f75acb00ad139599921d3237005d6b6a949b3dae/spec/support/shared_examples/v3_service_binding_create.rb#L22-L30
CreateDeleteAsyncInstanceWithSyncBackingServiceKeysAcceptanceTest:
service binding response without binding id
…b id to fallback."

This reverts commit 88c17002bec5d58748db9fdbf96a0c8d902c1985.
…ing V3 to get service instance in backing space, with potentially creating the space on the fly

Removed dead v2-based CSK
… rather try to contribute it to cf-java-client"

This reverts commit 2a2505cc78830ab7edd16ad000b281581b4ff279.
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

Successfully merging this pull request may close these issues.

Migrate to CAPI V3 API

2 participants