Feature/corporate maven repository

[gonzalad]

Hello, this PR should make it easier to use the library with a corporate maven repository.

The PR addresses:

• Make it easy to use with a private maven repository #835).
• [BUG] The version manager does not respect the NO_PROXY environment variable. #652

@wing328 or @kay-schecker is it possible for you to review this PR please ?

Contents of this PR:

1. fix NO_PROXY issue
   This is done by removing explicit handling of HTTP_PROXY and HTTPS_PROXY: Axios already handles that (see https://github.com/axios/axios#request-config).
2. added generator-cli.http.rejectUnauthorized configuration to avoid the error unable to get local issuer certificate.
3. support using placeholders for environment variables in any configuration value.
   this will allow to use env vars to set credentials in the queryUrl or downloadUrl:
   Usage:

   {
     "$schema": "./node_modules/@openapitools/openapi-generator-cli/config.schema.json",
     "spaces": 2,
     "generator-cli": {
       "version": "7.9.0",
       "repository": {
         "downloadUrl": "https://${MVN_USERNAME}:${MVN_PASSWORD}@mynexus.com/repository/maven-proxy-group/${groupId}/${artifactId}/${versionName}/${artifactId}-${versionName}.jar"
       }
     }
   }
   
   

4. For people using a nexus registry for both npm and maven registry: add support for retrieving authToken in .npmrc and using the npm token to authenticate to the maven repository.
   • the credentials for connecting to maven repository (authToken) are retrieved from .npmrc file
     (the credentials used is the one matching the url of the maven server).
   • also, if strict-ssl is set to false in npmrc, then certificate verification is disabled
     Usage:

   {
     "$schema": "./node_modules/@openapitools/openapi-generator-cli/config.schema.json",
     "spaces": 2,
     "generator-cli": {
       "version": "7.9.0",
       "repository": {
         "downloadUrl": "https://mynexus.com/repository/maven-proxy-group/${groupId}/${artifactId}/${versionName}/${artifactId}-${versionName}.jar"
       },
       "useNpmrc": true
     }
   }
   

5. Fix for running unit tests on windows
6. Activates logging (I had some issues testing the library on a project, and the library didn't output any logs)

[wing328]

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/OpenAPITools/openapi-generator/graphs/contributors.

Let me know if you need help fixing it.

Ref: https://github.com/OpenAPITools/openapi-generator/wiki/FAQ#how-can-i-update-commits-that-are-not-linked-to-my-github-account

[wing328]

thanks for the PR

I wonder if you can break down this PR into 2 smaller PRs to address the following issues separately for easier review:

• Make it easy to use with a private maven repository #835
• [BUG] The version manager does not respect the NO_PROXY environment variable. #652

[gonzalad]

thanks for the PR

I wonder if you can break down this PR into 2 smaller PRs to address the following issues separately for easier review:

• Make it easy to use with a private maven repository #835
• [BUG] The version manager does not respect the NO_PROXY environment variable. #652

Sure
I'll break it down in 2 PRs this evening and will close this PR one once it is done.
I'll fix the commit link to my github account at the same time

Thanks !

[gonzalad]

Default proxy handling in axios has an issue (returns 400 Bad Request with some proxies), see axios/axios#5256.

Sorry, I didn't see that issue before.

Now, I understand why you didn't us the default proxy handling from axios.

This PR should fix the issue #781.

I did some basic tests with some similar code, and it works.

I'll do more tests with the code from this PR and will keep you informed.

[gonzalad]

thanks for the PR

I wonder if you can break down this PR into 2 smaller PRs to address the following issues separately for easier review:

• Make it easy to use with a private maven repository #835
• [BUG] The version manager does not respect the NO_PROXY environment variable. #652

@wing328 : I tested PR #781 in my corporate environment and it works great (it supports NO_PROXY handling), could #781 be merged ?

[wing328]

@wing328 : I tested PR #781 in my corporate environment and it works great (it supports NO_PROXY handling), could #781 be merged ?

thanks for testing it

will merge once the merge conflicts are resolved