Skip to content

Migrate to CAPI V3 API #44

@gberche-orange

Description

@gberche-orange

Expected behavior

Observed behavior

Osb-cmdb 1.x uses CAPI V2 API in production and acceptance code base.

The design however does not rely too tightly on CAPI V2 specifics, in particular error recovery does not rely on CAPI V2 error codes and should port more easily on CAPI V3 apis.

CAPI V3 APIs are now complete

See associated design docs extracted from V3 API Proposals index

Resource Proposal Tracker Epic
[...]
Service Bindings & Keys https://docs.google.com/document/d/115XMaCGvtkuXpmSA-UwnEowYdZ75mLB_OdXsuSiwRf4/edit  
Service Brokers https://docs.google.com/document/d/1O-KMT9klgmnJtBtEHsKDV2IEOtZlG6TK3j68A8klMlk/edit https://www.pivotaltracker.com/epic/show/4450110
Service Instances https://docs.google.com/document/d/1P5laZqVYjtl_boSdpksT5LHOFjhm6CQLzWVx24UpXpM/edit  
Service Offerings https://docs.google.com/document/d/1bDsEiZRwQJNUI41cQlUaioY7JA1fnv_AThOI2ekPXNM/edit https://www.pivotaltracker.com/epic/show/4443887
Service Plans and  Service Plan Visibilities https://docs.google.com/document/d/1dwNbNy99f1qgKRfHy9hmc7B82XtcAtn0Wjg3KUpf7fo/edit  

However, support in cf-java-client is not yet complete:

Steps for osb-cmdb CAPI V2 EOL:

Affected release

Reproduced on version 1.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedblocked by missing dependencies/prerequisites

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions