openstack
/
mistral
Code Issues Proposed changes
mistral/mistral/engine
History
Renat Akhmerov 87c63f4206 Remove a TODO comment about saving an action spec 
* It's clear now that we don't have to store an action specification
  as part of the corresponding action execution object because
  the notion of action specification itself is specific for a certain
  type of action. In our case, ad-hoc actions.
  All changes recently made in the Mistral layers above the engine
  prove the correctnes of this thought. The comment can be safely
  deleted.

Change-Id: I45b97b08184c8d5a88bcc537fb5b1e538f105554
 		2020-10-05 17:22:28 +07:00
..
__init__.py Renaming "engine1" to "engine" 2015-04-09 17:47:36 +06:00
action_handler.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
actions.py Remove a TODO comment about saving an action spec 2020-10-05 17:22:28 +07:00
base.py Remove usage of six.add_metaclass 2020-09-19 11:37:24 +08:00
default_engine.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
dispatcher.py Performance: remove unnecessary workflow execution update 2018-09-03 11:47:11 +07:00
engine_server.py Add "convert_output_data" config property for YAQL 2020-02-13 17:31:41 +07:00
policies.py Remove six library 2020-09-23 10:27:12 +08:00
post_tx_queue.py Init profiler in for a new thread in post_tx_queue.py 2020-02-07 13:42:55 +07:00
task_handler.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
tasks.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
utils.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
workflow_handler.py Refactor task policies 2020-06-01 14:05:49 +07:00
workflows.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00