From f7b3c23bec2435f7f4ca9838fc6377d3d5249116 Mon Sep 17 00:00:00 2001
From: Joshua Harlow <harlowja@gmail.com>
Date: Wed, 18 Mar 2015 22:01:59 -0700
Subject: [PATCH] Expose the storage backend being used

To match how the persistence connections
provide access to there backend it seems
appropriate to also have the storage layer
provide the same property so that users of
it can easily access the underlying backend
object (if they so need to).

Change-Id: I8fdb5e7efc66bba93da2949bb6adad534bf3b127
---
 taskflow/storage.py | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/taskflow/storage.py b/taskflow/storage.py
index a08706c3..bb9f0a21 100644
--- a/taskflow/storage.py
+++ b/taskflow/storage.py
@@ -271,6 +271,11 @@ class Storage(object):
         # This never changes (so no read locking needed).
         return self._flowdetail.uuid
 
+    @property
+    def backend(self):
+        # This never changes (so no read locking needed).
+        return self._backend
+
     def _save_flow_detail(self, conn):
         # NOTE(harlowja): we need to update our contained flow detail if
         # the result of the update actually added more (aka another process