Add an API that gets an ad-hoc action DSL and validates it.
This is done in the same way workflows are validated today.
Change-Id: Ibbb949ef38befae1ef83a2a56cda4c817ceb41d4
Implements: blueprint validate-ad-hoc-action-api
After pip upgrading following error has occured during
mistral installation:
Invalid requirement, parse error at "'[-e]'"
I assume that this is because of extra '-e' flag that was passed
in mistral script and that is redundant ('-e' flag will be added
automatically in setup_develop function).
Change-Id: Ifed16935b045c723881a9da157a8759eea421c2c
* Clear separation for problems that can be handled so that the program
can continue and problems that can't handled automatically due to major
issues in configuration, environment or code itself
* Split YAQL exceptions into two types: grammar exception and evaluation
exception
* General NotFoundException is replaced with more specific DBEntryNotFoundException
for better consistency with other DB exceptions and more clear semantics
* Fixed corresponding tests
Change-Id: I07f495ab316b0f164caece78b1f101219199e68c
Implements: blueprint mistral-engine-error-handling
* Method rerun_workflow() was missing in Engine interface
* Renamed parameters in the hierarchy to be more consistent
* Added missing docstrings
Change-Id: I08b2b552130fd16a20f6647349006939619b6659
* Base class for API tests was called "FunctionalTest" which is
no longer a valid name (module itself is in "api" package).
Renamed it from FunctionalTest to APITest to reflect its meaning
better.
* Changed unit test for expiration policy so it does not inherit from
APITest because it doesn't need to. DBTestCase as a parent is enough.
Change-Id: Ia86da0df49c4170e19520ee62528a6772fdec641
* API unit tests activated cron trigger thread whereas all unit tests
assume that it's not started. Tests where it needs to be activated
should do it explicitly and shut down it after completion.
This was causing unpredictable results where we were assuming that
there weren't any active cron trigger threads.
* Minor cosmetic changes
Change-Id: I7e30f80b29520e03f2e1673788c764aabe1e4a8b
Closes-Bug: #1564353
While running tempest tests over https, warnings
are shown for unverified HTTPS request beacause
by default urllib3 don't verify ssl certificates.
So now, certification validation warnings have been
disabled.
Change-Id: I0e99af8364e262baa37a56b0a8846abde3a8d2b0
Closes-bug: #1570451
In version of oslo.messaging > 4.6.1, the __call__ method of
dispatcher.RPCDispatcher no longer exists. It is now a 'method-wrapper'
from the "object" object.
Calling inspect.getargspec on a method-wrapper doesn't work
TypeError: <method-wrapper '__call__' of ABCMeta object at 0x2cc3650> is not a Python function
Change-Id: Ie2ca1a2b9163a5edfe1e779cff462692197a471d
* Before this change there was a possibility of conflicts between
different tests working with cron triggers, especially if run
in parallel, because of using same trigger names (e.g. 'test').
To prevent such potential situations all trigger names should
be unique and generated randomly.
Change-Id: I57b0ac8072ab5f9158547fa0611a1003d1dc5e8a
Partial-Bug: #1564353
This patch fix the dir_path that helps to get the directory of
Mistral resources.
Without this patch, this is what we get when running Tempest:
IOError: [Errno 2] No such file or directory:
'/usr/lib/python2.7/site-packages/mistral_mistral/tests/resources/openstack/action_collection_wb.yaml'
With this patch:
/usr/lib/python2.7/site-packages/mistral/tests/resources/openstack/action_collection_wb.yaml
This path is correct and Tempest runs successfully.
Change-Id: Ie4bd3db8a4e729f7937a6f3c099d7c25abffcb1b
Closes-Bug: #1568413
* Added methods like await_workflow_state() and await_task_state() to
avoid using complex constructs based on _await() methods and lambdas.
* Minor style changes
Change-Id: I7f79ec819c955a5a624ff4d103bf6e97b30d9b91
