With this PR [1] we introduced stages into the test-operator role and the ability to run arbitrary hooks in between the stages. This requirement was asked by few teams (for example NFV). The current implementation does not solve two issues:

• hook duplicity
  • There shouldn't be two hooks that solve the same problem.
• justification of existence of each hook
  • The hook should exist only in case there is good enough justification for its existence. Meaning we explained why the functionality implemented by the hook can not be part of the framework executed by the test-operator role.

One potential solution is to have a common place for all the hooks that would allow to share hooks between the teams and review them properly and justify their existence.

DoD:

• We agreed what is the solution for the two problems (hook duplicity, justification of the existence of the hook)
• We implemented the solution.

[1] https://github.com/openstack-k8s-operators/ci-framework/pull/2374