Actions
Feature #12831
openProvide DSL and interface objects for expected errors
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
It would be nice if we'd have unified interface for all foreman tasks (not just dynflow based) so at the end we could call something like
@task.failed_on?(RemoteExecution::SecurityException) # maybe with optional boolean argument to check all errors to be the same exception
@task.failing_message
we can get similar data from dynflow based tasks by accessing the
@task.execution_plan.errors.first.exception_class
@task.execution_plan.errors.first.message
but the API should be the same, also note that dynflow tasks can have more than one exceptions
Also we should define the generic error interface objects that can be used in generic foreman tasks and that should become predecessors/included modules in Dynflow::ExecutionPlan::Steps::Error
Updated by Marek Hulán about 9 years ago
- Blocks Bug #12832: Improve template invocation status reporting added
Updated by Marek Hulán over 8 years ago
- Blocks Bug #14772: Exception is raised during hosts resolving if user does not have permissions to perform remote execution added
Actions