[ENH] Update trigger settings for local Kubernetes test #1286
Labels
area:developer-experience 👩🏻💻
needs: discussion 💬
Needs discussion with the rest of the team
needs: follow-up 📫
Someone needs to get back to this issue or PR
I am opening this issue as a matter of discussion. The current trigger aspect of the Kubernetes test is the following:
Though it does its work on validating that any change made into qhub infrastructure-related config is fully* tested -- by fully I mean an end-to-end deployment for Minikube Qhub. This sometimes can become a long waiting process over changes that are not entirely subject to a Qhub deployment. For example, in this recent #1282 if you look at the changes, you will see that there is no need for a full deployment of Qhub (its contrapositive to test this) in this case.
My main points over the current structure are:
So I would like to change the above trigger conditions to only trigger by direct changes in the package configuration or the terraform stages:
Would like to know what everyone think
The text was updated successfully, but these errors were encountered: