swagger-api / swagger-api/swagger-codegen
Swagger Remote URL Trust All for maven
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Can some one tell me how can I specify the arg for trusting all remote url in maven.
<plugin>
<groupId>io.swagger</groupId>
<artifactId>swagger-codegen-maven-plugin</artifactId>
<version>2.2.3</version>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<inputSpec>swagger.yaml</inputSpec>
<language>java</language>
<library>resttemplate</library>
</configuration>
</execution>
</executions>
</plugin>
How can I add -Dio.swagger.parser.util.RemoteUrl.trustAll=true to the plugin ?
I want it something like
<plugin>
<groupId>io.swagger</groupId>
<artifactId>swagger-codegen-maven-plugin</artifactId>
<version>2.2.3</version>
<arg>-Dio.swagger.parser.util.RemoteUrl.trustAll=true</arg>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<inputSpec>swagger.yaml</inputSpec>
<language>java</language>
<library>resttemplate</library>
</configuration>
</execution>
</executions>
</plugin>
Also is there a way I can specify inputSpec as a System Property of buildTime arg instead of fixing it. I am using a remote URL which changes based on environment
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 with the swagger-codegen-maven-plugin configuration shown in the issue and trace how its generate goal receives inputSpec and JVM properties. Determine whether Maven configuration can expose the remote URL trust setting and an environment-dependent inputSpec; done means both values work during plugin execution without being fixed in the POM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100