Closed RothAndrew closed 1 year ago
I can't argue with anything here. We did take a stab in the gilab capability with using the github action that dubbd uses to spin up a test k3d cluster for use. https://github.com/defenseunicorns/uds-capability-gitlab/blob/main/.github/workflows/build-test.yml. That seems to work pretty well.
But I understand the desire to have the tests be the same for local and ci.
How do we address testing across the other k8s distros and environments?
How do we address testing across the other k8s distros and environments?
TBD. The existing pattern is Terratest, which I'm still a fan of.
Waiting to merge until more people see this and have a chance to respond to it.
@RothAndrew have you compared the proposed solutions here to what is being used across the rest of the UDS effort? While we might not use the same shared workflows off-the-bat, the solutions will eventually converge.
@RothAndrew have you compared the proposed solutions here to what is being used across the rest of the UDS effort? While we might not use the same shared workflows off-the-bat, the solutions will eventually converge.
Yes
Based on the conversation we had I'm going to go create the PR for this in the UDS repo (will try and figure out some way of designating that it is a SWF-specific decision), then I'll close this PR.
OBE. Replaced by https://github.com/defenseunicorns/uds/pull/170
Create the ADR for how we intend for tests to be run, both locally and in CI.
This first draft is intended to stimulate discussion and debate, in the hopes that we come to a solution that the team likes and enjoys working with.