karbor/karbor/services/operationengine
jiaopengju bba93226e6 Add trigger verification in API
Currently, we use 'cast' instead of 'call' to send request
from api to operationengine when creating a new trigger.
With 'cast', it will not give a return value to api even the
trigger is invalid, so users can create triggers successfully
with using invalid triggers.

This patch add trigger verification in API side. Before send
create request to operationengine, API send a verify request
to operationengine first, which type is 'call', to make sure
the trigger will be created is valid.

Change-Id: Iea734e1b4a63f6e35afe32cbbb2b60f79d6db085
Closes-Bug: #1736657
2018-01-26 13:50:37 +08:00
..
engine Revert "Add time format check in API" 2018-01-08 09:27:37 +08:00
operations adding more protection parameters retention period 2017-11-13 03:56:01 +00:00
__init__.py Change Smaug to Karbor 2016-08-18 22:55:34 +08:00
api.py Add trigger verification in API 2018-01-26 13:50:37 +08:00
karbor_client.py Update the way of getting endpoint of other service 2017-01-25 17:06:37 +08:00
manager.py Add trigger verification in API 2018-01-26 13:50:37 +08:00
operation_manager.py Docs: enable warning-is-error, fix errors 2017-07-25 15:23:32 +03:00
rpcapi.py Add trigger verification in API 2018-01-26 13:50:37 +08:00
user_trust_manager.py Remove redundant ctor super calls, add missing 2017-05-14 12:10:31 +03:00