diff options
Diffstat (limited to 'docs/sections/services/pm-mapper')
-rw-r--r-- | docs/sections/services/pm-mapper/configuration.rst | 20 | ||||
-rw-r--r-- | docs/sections/services/pm-mapper/installation-helm.rst | 3 | ||||
-rw-r--r-- | docs/sections/services/pm-mapper/troubleshooting.rst | 2 |
3 files changed, 11 insertions, 14 deletions
diff --git a/docs/sections/services/pm-mapper/configuration.rst b/docs/sections/services/pm-mapper/configuration.rst index 2fd89a70..fbac01c7 100644 --- a/docs/sections/services/pm-mapper/configuration.rst +++ b/docs/sections/services/pm-mapper/configuration.rst @@ -25,7 +25,7 @@ Disable TLS Pm-mapper by default uses communication over TLS, but it is also possible to use plain http request. To disable TLS, set configuration flag 'enable_http' to true, and set the certificate paths to empty strings or remove them from the configuration. See the config.yaml examples below. .. code-block:: yaml - + applicationConfig: enable_http: true key_store_path: "" @@ -35,16 +35,16 @@ Pm-mapper by default uses communication over TLS, but it is also possible to use -Or +Or .. code-block:: yaml applicationConfig: enable_http: true - #key_store_path: - #key_store_pass_path: - #trust_store_path: - #trust_store_pass_path: + #key_store_path: + #key_store_pass_path: + #trust_store_path: + #trust_store_pass_path: Unauthenticated topic @@ -52,7 +52,7 @@ Unauthenticated topic To use unauthenticated topics :ref:`disable TLS <pm_mapper_disable_tls>`, and edit AAF credentials in configuration, it should be removed or set to empty string. See the examples below. .. code-block:: yaml - + applicationConfig: aaf_identity: "" aaf_password: "" @@ -61,10 +61,10 @@ To use unauthenticated topics :ref:`disable TLS <pm_mapper_disable_tls>`, and ed Or .. code-block:: yaml - + applicationConfig: - #aaf_identity: - #aaf_password: + #aaf_identity: + #aaf_password: diff --git a/docs/sections/services/pm-mapper/installation-helm.rst b/docs/sections/services/pm-mapper/installation-helm.rst index 04e7503d..badfb875 100644 --- a/docs/sections/services/pm-mapper/installation-helm.rst +++ b/docs/sections/services/pm-mapper/installation-helm.rst @@ -83,7 +83,7 @@ The configuration update process is very straightforward. The only step is to modify the Config Map which contains the configuration and save the change. PM-Mapper will detect the new configuration values after a while. It should be visible in PM-Mapper logs, for example: -.. code-block:: text +.. code-block:: none ... 2022-02-11T08:04:02.627Z main INFO org.onap.dcaegen2.services.sdk.rest.services.cbs.client.impl.CbsClientConfigMap Got successful output from ConfigMap file @@ -94,4 +94,3 @@ It should be visible in PM-Mapper logs, for example: This logs fragment proves that the configuration source is Config Map: ``Got successful output from ConfigMap file``. It also prints the current configuration (the last log line above). PM-Mapper keeps checking the configuration file periodically (every 60s). - diff --git a/docs/sections/services/pm-mapper/troubleshooting.rst b/docs/sections/services/pm-mapper/troubleshooting.rst index add7b7ae..444f7132 100644 --- a/docs/sections/services/pm-mapper/troubleshooting.rst +++ b/docs/sections/services/pm-mapper/troubleshooting.rst @@ -125,5 +125,3 @@ Make sure Config Binding Service is up and running and the **ip + port** combina **PM Mapper** logs this information when connected to Consul, but cannot find a valid JSON configuration. - - |