As discussed in https://github.com/canonical/charmed-kubeflow-workflows/pull/75#discussion_r1795300510, terraform-checks-solution.yaml is very similar to terraform-checks.yaml and we could unify those. However, terraform-checks.yaml is designed right now with charm-module specific limitations, which make it impossible to use it out of the box for solutions. We need thus to refactor those workflows and once this is done, update all our charm repositories (and branches) in order to follow the new API, since we expect breaking changes there.
What needs to get done
Redesign terraform-checks.yaml to work also for solutions
Update charm and solution modules to use the updated workflow
Context
As discussed in https://github.com/canonical/charmed-kubeflow-workflows/pull/75#discussion_r1795300510,
terraform-checks-solution.yaml
is very similar toterraform-checks.yaml
and we could unify those. However,terraform-checks.yaml
is designed right now with charm-module specific limitations, which make it impossible to use it out of the box for solutions. We need thus to refactor those workflows and once this is done, update all our charm repositories (and branches) in order to follow the new API, since we expect breaking changes there.What needs to get done
Definition of Done
All modules use a common and updated CI