openstack
/
mistral
Code Issues Proposed changes

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
This commit is contained in:
Renat Akhmerov 2020-10-05 17:22:28 +07:00
parent 175e5fd587
commit 87c63f4206
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
mistral/engine/actions.py
View File

@ -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,