Hi Anil,
>I think we should adopt an asynchronous model, where we maintain the state for
>>tap-service and tap-flow objects. Valid states could be "created",
>"create->pending" and "failed." In addition, we will need a suitable mechanism
>to have >the plugin extract the current state from the a
The current tap-service-* and tap-flow-* APIs are synchronous. When the call
completes a status of success or failure is returned. The problem here though
is that this status is being returned by the TaaS plugin after it goes through
some checks and successfully updates the configuration state.
