OpenAPITools / OpenAPITools/openapi-generator
[REQ] Feature Request Description
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
We would prefer to use a registry separate DockerHub for pulling the OpenAPI generator image.
Describe the solution you'd like
Please publish the Docker image to more registries than hub.docker.com. The GitHub container registry should be easy (I have done it for other images, such as: https://github.com/KineticCafe/docker-sqitch-pgtap/blob/main/.github/workflows/publish-release.yml). The public AWS ECR registry should not be difficult, but would be more work than adding GHCR.
Describe alternatives you've considered
Keep using the DockerHub image or mirroring it myself on a different registry. Having it come from an official OpenAPITools-supported registry would be preferred.
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
No repository file or test is named. Start by locating the existing workflow that publishes the DockerHub image and compare it with the linked example workflow; done means an official OpenAPITools image is published to an additional registry, with GitHub Container Registry identified as the initial target and AWS ECR considered separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100