Skip to content

chore: migrate to compute (formerly workload-operator) - #54

Open
scotwells wants to merge 1 commit into
mainfrom
chore/migrate-to-compute
Open

chore: migrate to compute (formerly workload-operator)#54
scotwells wants to merge 1 commit into
mainfrom
chore/migrate-to-compute

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Summary

Consumer-side migration for the repo rename in datum-cloud/compute#83 and the kustomize layout change in datum-cloud/compute#84.

  • Go module path updated: go.datum.net/workload-operator -> go.datum.net/compute
  • Pinned to compute v0.6.0 (first release on the new name)
  • README + devcontainer bind mount updated to reference the new repo name
  • Stale code comments referencing workload-operator refreshed

The CRD API group is unchanged (compute.datumapis.com with Workload, WorkloadDeployment, Instance), so no data migration is required and existing custom resources keep working.

This repo does not consume the compute kustomize bundle directly, so no Flux/overlay path changes (default -> overlays/single-cluster) were needed here.

Test plan

  • go mod tidy
  • go build ./...
  • go test ./...
  • go vet ./...
  • gofmt -w .
  • grep -r workload-operator returns zero hits
  • CI green

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

The workload-operator repo was renamed to compute. Update the Go
module path, pin to compute v0.6.0, and refresh docs/devcontainer
references. The CRD API group (compute.datumapis.com) is unchanged
so no data migration is required.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant