Today we had an offline discussion with the WSO2 API-M team on the current implementation of the API-M service broker and @lakwarus suggested to introduce a persistent storage for managing the mapping between the service bind id and api id which is currently managed on API-M side using the API description field.
Today we had an offline discussion with the WSO2 API-M team on the current implementation of the API-M service broker and @lakwarus suggested to introduce a persistent storage for managing the mapping between the service bind id and api id which is currently managed on API-M side using the API description field.
https://github.com/wso2/pivotal-cf-apim/blob/master/service-broker/wso2apim/cf/servicebroker/service-broker-api-utils.bal#L14 https://github.com/wso2/pivotal-cf-apim/blob/master/service-broker/wso2apim/publisher/api/client/publisher-api-client.bal#L48
We may either need to add a data storage to the service broker API or use a key value store for this purpose.