summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKrzysztof Opasiak <k.opasiak@samsung.com>2019-06-01 01:02:41 +0200
committerThomas Kulik <thomas.kulik@telekom.de>2021-05-03 06:57:39 +0000
commit8981c658fc5453c56c84b3af7744fb257699e769 (patch)
tree16cd14229c9c3c45bdbd6e9bf1a9dd24410de83f
parent0ed257d00053e1bca6fd0c56c222ee47d26cf952 (diff)
Add reference to OSA repo from main documentation page
In order to make it easy for users to find, let's add OSA reference to the main page of ONAP documentation Issue-ID: SECCOM-239 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I2c009a1a21289c2dd18f0e60122a24ec86aefb40 (cherry picked from commit 5c91534a6d304bf1076ab45e6010dfd490b2a9de)
-rw-r--r--docs/index.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/index.rst b/docs/index.rst
index e1f7e24f8..619af5f73 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -54,6 +54,9 @@ Please find some guidance here on the content of ONAP documentation:
| | and PNFs can accelerate the optimal usage of this ONAP environment. The guidelines |
| | on VNF/PNF requirements facilitates synchronized and aligned activities for all participants. |
+---------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------+
+ | :ref:`ONAP Security <onap-security>` | The current state of ONAP Security is described here. We can learn about discovered and fixed |
+ | | vulnerabilities. |
+ +---------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------+
.. toctree::