Add OCI Registry Repo Creation to Nebi API
Open
Nobody has claimed this yet.
needs: scoping
- Dominant language
- Go
- Stars
- 24
- Forks
- 9
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 33
Description
Registry Specific APIs
Repo creation is not part of the OCI spec so it will provide some provider-specific code for some providers.
| Registry | Repo Creation |
|---|---|
| Docker Hub | Implicit on push, or web UI |
| ghcr.io | Implicit on push |
| AWS ECR | Requires aws ecr create-repository first |
| Azure ACR | Implicit or via Azure API |
| Harbor | Has its own project/repo API |
| Artifactory | Requires pre-created repos |
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 by locating Nebi's API entry points and OCI registry integration, then identify how provider-specific operations are organized. Compare the existing provider behavior with the registry table, especially AWS ECR, Azure ACR, Harbor, and Artifactory. Done means the API supports the agreed repository-creation behavior for providers that require it while preserving implicit creation elsewhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, docker, go
- Domain
- backend-api-design, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100