Make it easy to use with a private maven repository
@kay-schecker is already working on this.
Since Oct 16, 2024.
Assessment
This issue has not been assessed yet.
Description
Hello,
I am using the openapi-generator-cli 2.14.0 with a private maven repository (requiring authentication).
Atm using this cli with this setup involves a few steps and makes it feel a bit quirky.
I was wondering if it's possible make the whole process smoother:
- fix NO_PROXY handling
- easier authentication to private maven repositories (no credentials hardcoded in the openapitools.json)
Steps to follow to use the openapi-generator-cli with a private maven repository
Here are the steps I needed to follow to make the openapi-generator-cli work in my corporate environment.
Please note: I am used to have HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment vars setup.
The NO_PROXY is set in order to avoid internal http calls to be sent via the proxy.
-
First run: I get a 503 (returned by my http proxy)
Ok, this is the issue https://github.com/OpenAPITools/openapi-generator-cli/issues/652
Fix: I remove all HTTP_PROXY, HTTPS_PROXY -
Second run: I get a unable to get local issuer certificate.
Ok, this is related to https://github.com/OpenAPITools/openapi-generator-cli/issues/130#issuecomment-737277129
Fix: I add NODE_TLS_REJECT_UNAUTHORIZED=0 as environment variable -
Third run: Request failed with status code 401 (returned by my private maven repository)
Fix: I hardcode my user/pwd credentials in my openapitools.json.
I am not too happy with this solution since I'll need to do some pre-processing to be able to others dev in my team to use their credentials (or for the ci to run):{ "$schema": "./node_modules/@openapitools/openapi-generator-cli/config.schema.json", "spaces": 2, "generator-cli": { "version": "7.9.0", "repository": { "downloadUrl": "https://myuser:mypassword@my.corporate.maven.repo.com/repository/mvn-proxy-group/${groupId}/${artifactId}/${versionName}/${artifactId}-${versionName}.jar" } } }
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 208
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
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.
More from OpenAPITools/openapi-generator-cli
-
[FEATURE] consider using caret ranges instead of pinned exact versions for runtime dependencies Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
OpenAPITools/openapi-generator-cli#1213 · 1 assignee ·
-
bug
OpenAPITools/openapi-generator-cli#1190 · 1 assignee ·
-
bug
OpenAPITools/openapi-generator-cli#1138 · 1 comment · 1 assignee ·
-
bug
OpenAPITools/openapi-generator-cli#1094 · 1 comment · 1 assignee ·
All issues in OpenAPITools/openapi-generator-cli
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100