Enable pinning our charm test dependencies (ex: if kubeflow-dashboard
's tests need to deploy kubeflow-profiles
)
#136
Labels
enhancement
New feature or request
Context
Most MLOps charms have integration tests that have dependencies on other charms (for example, the kubeflow-dashboard charm requires the kubeflow-profiles charm) . The channel for these dependencies is hard-coded in the test files , generally pointing to latest/edge. This causes three issues:
Item (2) is a cost on developer time as well as a source for bugs passing through CI into released charms. Items (1) and (3) are a cost on developer time.
What needs to get done
tox -e integration -- --dependency-bundle bundle.yaml
wherebundle.yaml
specifies the dependency versions that should be used1.8
release branch to the kubeflow-profiles dependency to1.8/stable
instead oflatest/edge
Definition of Done
The text was updated successfully, but these errors were encountered: