Automatically generate Swagger documentation

[skdong]

[document] Swagger Rest API adoc (#150)(#176)

• Add SwaggerConfig to activate Swagger documentation when mvn test
• Add SwaggerJsonTest unit test for call Swagger API generating Swagger adoc documentation
• Swagger adoc documentation generated under target/swagger directory

[xieus]

@skdong The PR description looks pretty comprehensive. We only need to run "mvn test" to create the swagger adoc which will be generated under target/swagger directory, is that correct?

Also, do we still need the other PR #177?

[skdong]

@xieus yes We only need to run "mvn test" to create swagger adoc

[skdong]

@xieus This PR generates a Swagger adoc. Swagger generates documents through Spring Controller. PR # 177 generates adoc for each unit test. There is no corresponding Spring Controller for apigateway type api. It needs to be generated for unit test

[xieus]

@skdong Thanks for the response. I just tried to run "mvn test" in the swagger-auto branch, I didn't find the target/swagger sub-directory showed up. Something I might have missed?

[skdong]

@xieus This is because I turned off the unit test, the operation of generating the document was completed in a unit test, and now the unit test still depends on the database.

[skdong]

@xieus I can open the unit test and submit it, but It need to have a connectable database.

[xieus]

The Ignite UT issue is kind of headache. We will have to live without Ignite UTs until the issue is fixed. @chenpiaoping could you please take a look? This is becoming a blocking issue for us.

[xieus]

@skdong You should be unblocked. UTs are enabled (see PR #186)

[skdong]

@xieus Ok I will unblock it

[skdong]

@xieus I only activated Uts of route, subnet, vpc, these microservices are normal now. Mac and private IP UTs still have errors when executed

mac microservice tips com.futurewei.alcor.common.db.CacheFacotry confilicts with com.futurewei.alcor.common.service.CacheFacotry

Private ip microservice prompt Unable to connect to localhost: 6379

[xieus]

LGTM.

[xieus]

@xieus I only activated Uts of route, subnet, vpc, these microservices are normal now. Mac and private IP UTs still have errors when executed

mac microservice tips com.futurewei.alcor.common.db.CacheFacotry confilicts with com.futurewei.alcor.common.service.CacheFacotry

Private ip microservice prompt Unable to connect to localhost: 6379

@skdong I think the current PR looks good, and the Mac Manager and IP Manager UTs error could be fixed by service owner.

@kimeunju108 please look into the Mac Manager UTs, and @chenpiaoping please look into the IP manager UTs.