Closed chizhg closed 3 years ago
/lgtm
one quick question: there's probably more value in actually exporting the non-deployer "helper" functions (i.e. network setup etc.)
Usability of deployers as libraries is questionable considering the contract between deployers and testers is still binary invocation.
The major/only reason we want this change is to decouple the different steps (project setup, network setup, cluster creation, etc.) in the pipeline, so that we can run each step individually.
We are not planning to rebuild a new pipeline by calling these public functions, that'll be still orchestrated by the kubetest2 binary.
Does it answer your question?
My main question is around how we plan to use the public deployer functions. If users still needs to construct the kubetest2 gke deployer then it's probably less ideal than exporting the networking pieces directly.
But either way, this will help in making these methods reusable by users who want to manage the network lifecycle on their own.
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: amwat, chizhg
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
Change the functions for kubetest2-gke deployer to public, so that it can be used as a library.