Actions
Refactor #9508
closedBetter support for triggering sub plans from run phase and waiting for them to finish
Description
Sometimes, it's better to extract a part of the execution plan to a separate task.
The usecases are:
1. some information required in plan phase not available when the whole task starts
2. other logic in the system requiring the action to be represented as separate task (such as repository syncing)
3. bulk actions
We already have the logic in place for bulk action. Let's extract that to some common parent action
so that others can benefit from that as well
Updated by The Foreman Bot over 10 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/99 added
- Pull request deleted (
)
Updated by Ivan Necas about 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 131f05b6fcc027d071cc4ad71610827f7dff9161.
Actions