Project

General

Profile

Feature #12831

Provide DSL and interface objects for expected errors

Added by Marek Hulán over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

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


Related issues

Blocks Foreman Remote Execution - Bug #12832: Improve template invocation status reportingNew2015-12-15
Blocks Foreman Remote Execution - Bug #14772: Exception is raised during hosts resolving if user does not have permissions to perform remote executionNew2016-04-21

History

#1 Updated by Marek Hulán over 6 years ago

  • Blocks Bug #12832: Improve template invocation status reporting added

#2 Updated by Marek Hulán over 6 years ago

  • Blocks Bug #14772: Exception is raised during hosts resolving if user does not have permissions to perform remote execution added

Also available in: Atom PDF