CP 2.0: Phase 1: refactor manifest deletion to be purely dynflow
The current manifest operations use a combination of legacy and dynflow orchestration. This issue should refactor the logic to utilize only dynflow.
#4 Updated by David Davis over 4 years ago
- Subject changed from CP 2.0: Phase 1: refactor manifest import/refresh to be purely dynflow to CP 2.0: Phase 1: refactor manifest deletion to be purely dynflow
I'm assuming this should be deletion as we already have an import/fresh task: