Deprecate `engine_conf` and prefer `engine` instead

To avoid having one set of options coming from `engine_conf`
and another set of options coming from `kwargs` and another set
coming from `engine_conf` if it is a URI just start to shift
toward `engine_conf` being deprecated and `engine` being a string
type only (or a URI with additional query parameters) and having
any additional **kwargs that are provided just get merged into the
final engine options.

This adds a new helper function that handles all these various
options and adds in a keyword argument `engine` that will be shifted
to in a future version (in that future version we can also then
remove the `engine_conf` and just stick to a smaller set of option
mechanisms).

It also adjusts all examples to use this new and more easier to
understand format and adjusts tests, conductor interface to use
this new more easily understandable style of getting an engine.

Change-Id: Ic7617057338e0c63775cf38a24643cff6e454950

1 files changed, 1 insertions, 5 deletions

diff --git a/taskflow/examples/resume_volume_create.py b/taskflow/examples/resume_volume_create.py
index 0fe502e..275fa6b 100644
--- a/taskflow/examples/resume_volume_create.py
+++ b/taskflow/examples/resume_volume_create.py
@@ -143,13 +143,9 @@ with example_utils.get_backend() as backend:
         flow_detail = find_flow_detail(backend, book_id, flow_id)
 
     # Load and run.
-    engine_conf = {
-        'engine': 'serial',
-    }
     engine = engines.load(flow,
                           flow_detail=flow_detail,
-                          backend=backend,
-                          engine_conf=engine_conf)
+                          backend=backend, engine='serial')
     engine.run()
 
 # How to use.