commit 87c63f4206e32fd1fd7ff793afc664a567a2deba
Author: Renat Akhmerov <renat.akhmerov@gmail.com>
Date:   Mon Oct 5 17:22:28 2020 +0700

    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

diff --git a/mistral/engine/actions.py b/mistral/engine/actions.py
index 3834550..3f9d273 100644
--- a/mistral/engine/actions.py
+++ b/mistral/engine/actions.py
@@ -163,8 +163,6 @@ class Action(object, metaclass=abc.ABCMeta):
         values = {
             'id': action_ex_id,
             'name': self.action_desc.name,
-            # TODO(rakhmerov): do we really need to keep "spec" in action_ex?
-            # 'spec': self.action_desc.spec,
             'state': states.RUNNING,
             'input': input_dict,
             'runtime_context': runtime_ctx,