summaryrefslogtreecommitdiffstats
path: root/docs/development
diff options
context:
space:
mode:
authorAjith Sreekumar <ajith.sreekumar@bell.ca>2022-04-22 12:16:49 +0000
committerGerrit Code Review <gerrit@onap.org>2022-04-22 12:16:49 +0000
commit5ace6230a31c93910acdf524015578187c9e1761 (patch)
tree01f144da8a5e0642dcc4628462bb38f1c543d044 /docs/development
parent7cceef2d644dabd297451ed8dfe85206d22c51fb (diff)
parent2061a3615aa6e8d6810b9ac74402726ce077668e (diff)
Merge "Document changes for API springboot migration"
Diffstat (limited to 'docs/development')
-rw-r--r--docs/development/devtools/devtools.rst19
1 files changed, 17 insertions, 2 deletions
diff --git a/docs/development/devtools/devtools.rst b/docs/development/devtools/devtools.rst
index 787af683..9012caf8 100644
--- a/docs/development/devtools/devtools.rst
+++ b/docs/development/devtools/devtools.rst
@@ -253,9 +253,10 @@ running MariaDb database instance. The easiest way to do this is to run the dock
information on doing so. Once the mariadb is up and running, a configuration file must be provided to the api in order for it to know how to
connect to the mariadb. You can locate the default configuration file in the packaging of the api component:
-`Default API Configuration <https://gerrit.onap.org/r/gitweb?p=policy/api.git;a=blob;f=packages/policy-api-tarball/src/main/resources/etc/defaultConfig.json;h=042fb9d54c79ce4dad517e2564636632a8ecc550;hb=refs/heads/master>`_
+`Default Policy API Configuration <https://gerrit.onap.org/r/gitweb?p=policy/api.git;a=blob;f=packages/policy-api-tarball/src/main/resources/etc/apiParameters.yaml;h=2c19199a8a889cb0ab203334182662fe15e1635e;hb=refs/heads/master>`_
-You will want to change the fields pertaining to "host", "port" and "databaseUrl" to your local environment settings.
+You will want to change the fields pertaining to "host", "port" and "databaseUrl" to your local environment settings and start the
+policy-api springboot application either using your IDE of choice or using the run goal from Spring Boot Maven plugin: *mvn spring-boot:run*.
Running the API component using Docker Compose
++++++++++++++++++++++++++++++++++++++++++++++
@@ -347,6 +348,10 @@ the Policy Framework works in a full ONAP deployment.
Generating Swagger Documentation
********************************
+
+1. Using Swagger2Markup maven plugin from Policy Parent Integration POM
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
The `Policy Parent Integration POM <https://github.com/onap/policy-parent/blob/master/integration/pom.xml>`_ contains a *generateSwaggerDocs* profile. This
profile can be activated on any module that has a Swagger endpoint. When active, this profile creates a tarball in Nexus with the name
*<project-artifactId>-swagger-docs.tar.gz*. The tarball contains the following files:
@@ -394,6 +399,16 @@ of such a test case.
See `this unit test case <https://github.com/onap/policy-clamp/blob/master/runtime/src/test/java/org/onap/policy/clamp/clds/it/HttpsItCase.java>`_
for the full example.
+2. Accessing Swagger documentation for springboot based policy applications
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+Springfox Swagger2 maven dependency aids with auto-generation of Swagger documentation.
+
+Using the Swagger-UI maven dependency Swagger HTML documentation can be accessed at the root url.
+
+- The generated swagger.json can be accessed at: *https://service_IP:service_port/v2/api-docs*
+- Swagger UI can be accessed at: *https://service_IP:service_port/swagger-ui/index.html*
+
Running the DMaaP Simulator during Development
**********************************************
It is sometimes convenient to run the DMaaP simulator during development. You can run it from the command line using Maven or from within your IDE.