While developing new playbooks or extending existing playbooks one often has to wait a few seconds/minutes until edi starts to process the modified playbook within the (emulated) container. There are already possibilities to skip the bootstrapping etc. (e.g. by using --recursive-clean 4 while doing image builds) but if the modified playbook is one of the last playbooks it still takes a while to get to the modified playbook.
Desired Behavior
There should be a way to "fast forward" to the modified playbook. The assumption is that this will be a debug feature and the developer is a power user.
Let's assume that we have four playbooks (A, B, C and D) and the playbooks A and B were executed successfully but due to modifications playbook C fails. The goal is now to fix playbook C and then directly jump to it by skipping playbook A and B. The assumption is that the (temporary) container is still running and that playbook A and B would anyway not change anything due to idempotency. However, after playbook C got finally fixed also playbook D should get executed and all subsequent steps of the pipeline.
As a hint edi could print the debug options in case of a playbook failure. Overall this would be very beneficial for efficient playbook development.
Issue Type
Actual Behavior
While developing new playbooks or extending existing playbooks one often has to wait a few seconds/minutes until edi starts to process the modified playbook within the (emulated) container. There are already possibilities to skip the bootstrapping etc. (e.g. by using --recursive-clean 4 while doing image builds) but if the modified playbook is one of the last playbooks it still takes a while to get to the modified playbook.
Desired Behavior
There should be a way to "fast forward" to the modified playbook. The assumption is that this will be a debug feature and the developer is a power user. Let's assume that we have four playbooks (A, B, C and D) and the playbooks A and B were executed successfully but due to modifications playbook C fails. The goal is now to fix playbook C and then directly jump to it by skipping playbook A and B. The assumption is that the (temporary) container is still running and that playbook A and B would anyway not change anything due to idempotency. However, after playbook C got finally fixed also playbook D should get executed and all subsequent steps of the pipeline.
As a hint edi could print the debug options in case of a playbook failure. Overall this would be very beneficial for efficient playbook development.