COAB does not manage state in a database, it relies instead on OSB API support for service instance operations in which it stores its next step to execute after the coa deplyment completes. Support inner broker would require to either
also track whether during each polling an inner service instance is currently in progress
Expected behavior
As a coab service broker author
Observed behavior
async-supported=false
in provisionning requests and does not issuelast-operation
callshttps://github.com/orange-cloudfoundry/cf-ops-automation-broker/blob/9b6a7a33881c9f8ab8d6f79358d204c5afed69fa/cf-ops-automation-broker-core/src/main/java/com/orange/oss/cloudfoundry/broker/opsautomation/ondemandbroker/pipeline/OsbProxyImpl.java#L258
operations
in which it stores its next step to execute after the coa deplyment completes. Support inner broker would require to eitheroperations
in the GET /v2/service_instances/:instance_id/last_operation response. This would likely require to introduce a cache/db for coab to maintain its state machine