You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrate the Workload API-acceptance contract test out of datum-cloud/infra
into the owning repo, per datum-cloud/infra#3006. That issue consolidates
infra's live-env Chainsaw suite into one "construct" group and evacuates
single-service compute.datumapis.com contract tests to compute, run against
the local kind harness pre-merge.
This test applies a Workload (plus networking Location/Network fixtures) and
asserts the control plane accepts and stores the Workload — API schema and
admission only, no wait for VM provisioning.
Key changes:
- Add test/e2e/workload-api-acceptance/ with the chainsaw test and the
location.yaml / network.yaml / workload.yaml fixtures copied from infra.
- Drop the datumctl auth update-kubeconfig setup step and the project
control-plane cluster block; target a local kind cluster via spec.cluster,
mirroring datum-cloud/network-services-operator.
- Remove spec.skip: true.
- Introduce a minimal, WIP chainsaw harness to the Makefile: kind + chainsaw
tool vars, install targets, and a test-chainsaw target that runs chainsaw
against the kind cluster. Compute has no chainsaw setup today; this is a
proposed harness pending compute-team decision on chainsaw vs. extending
the existing Go e2e suite.
0 commit comments