This check become useless. We are currently creating the list of operations from the dag and eventually assign them a playbook if define. Dag operations with no associated playbook are then treated as "noop". Hence, we are not using the noop property anymore.
Furthermore, this check doesn't cover the case where a noop is defined in collection1 and then is completed with a playbook defined in collection2.
I suggest to also remove entirely the noop property from the dag files (in the collections) are it is not used anymore.
Which issue(s) this PR fixes
Fixes None
Additional comments
This check become useless. We are currently creating the list of operations from the dag and eventually assign them a playbook if define. Dag operations with no associated playbook are then treated as "noop". Hence, we are not using the
noopproperty anymore.Furthermore, this check doesn't cover the case where a noop is defined in
collection1and then is completed with a playbook defined incollection2.I suggest to also remove entirely the
noopproperty from the dag files (in the collections) are it is not used anymore.Agreements