wso2 / wso2/open-cloud-datacenter
[Task]: CI for the registry operator
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 19
- Forks
- 15
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 4
Description
Description
registry/ has no workflow. Nothing builds it runs its tests or checks that generated manifests match their source. Every check in PR #285 and its follow-up was run by hand which is not a claim a release can rest on.
The sibling operator keyvault has the template to follow.
Acceptance criteria
- A registry-operator workflow triggered on pull requests and pushes that touch registry/.
- Runs go build, go vet, gofmt -l and go test ./... -count=1.
- Fails when make manifests generate produces a diff. So generated files cannot drift from their source.
- On the operators branch builds and pushes the image to ghcr.io tagged by commit.
- Test failures block the merge.
Verification
Open a pull request with a deliberately unformatted file and a stale CRD both are caught.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in registry/ and compare the sibling keyvault operator's workflow template. Check the existing make manifests target, then verify the workflow runs go build, go vet, gofmt -l, and go test ./... -count=1 while rejecting generated-file diffs. Done means pull requests and relevant pushes are checked, and the operators branch publishes an image to ghcr.io tagged by commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 70/100