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
However, support in cf-java-client is not yet complete:
Steps for osb-cmdb CAPI V2 EOL:
Affected release
Reproduced on version 1.0
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
However, support in cf-java-client is not yet complete:
Steps for osb-cmdb CAPI V2 EOL:
Affected release
Reproduced on version 1.0