summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorJim Hahn <jrh3@att.com>2021-03-30 15:09:11 -0400
committerJim Hahn <jrh3@att.com>2021-03-30 15:13:35 -0400
commit382cedafbeb122aa36a34fa1280b8134581fedd1 (patch)
treeac4eb9ec8d60c678539afcb51e4848feab4f0570 /docs
parent5db08bd661c5e7c92f4bc211c6f56421a9439946 (diff)
Fix some broken documentation links
Issue-ID: POLICY-3164 Change-Id: I994e1043ec4af385a69c977cd3f2264992376a11 Signed-off-by: Jim Hahn <jrh3@att.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/architecture/architecture.rst2
-rw-r--r--docs/release-notes.rst12
2 files changed, 7 insertions, 7 deletions
diff --git a/docs/architecture/architecture.rst b/docs/architecture/architecture.rst
index 4c8b3f7b..7edf9e07 100644
--- a/docs/architecture/architecture.rst
+++ b/docs/architecture/architecture.rst
@@ -393,7 +393,7 @@ this information to automatically generate a policy.
Note that SDC provides a wrapper for the SDC API as a Java Client and also provides a TOSCA parser. See the
documentation for the `Policy Distribution Component
-<https://docs.onap.org/en/latest/submodules/policy/distribution.git/docs/index.html>`__.
+<https://docs.onap.org/projects/onap-policy-parent/en/latest/distribution/distribution.html>`__.
In Step 4 above, the \ *PolicyDesign* must download the CSAR file. If the policy is to be composed from the TOSCA
definition, it must also parse the TOSCA definition.
diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 7e36b3e3..852498d2 100644
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -89,7 +89,7 @@ System Limitations
The policy API component requires a fresh new database when migrating to the honolulu release.
Therefore, upgrades require a fresh new database installation.
Please see the
-`Installing or Upgrading Policy <https://onap.readthedocs.io/en/latest/submodules/policy/parent.git/docs/installation/oom.html#installing-or-upgrading-policy>`__ section for appropriate procedures.
+`Installing or Upgrading Policy <https://docs.onap.org/projects/onap-policy-parent/en/honolulu/installation/oom.html#installing-or-upgrading-policy>`__ section for appropriate procedures.
Known Vulnerabilities
~~~~~~~~~~~~~~~~~~~~~
@@ -225,7 +225,7 @@ System Limitations
The policy API component requires a fresh new database when migrating to the guilin release.
Therefore, upgrades require a fresh new database installation.
Please see the
-`Installing or Upgrading Policy <https://onap.readthedocs.io/en/latest/submodules/policy/parent.git/docs/installation/oom.html#installing-or-upgrading-policy>`__ section for appropriate procedures.
+`Installing or Upgrading Policy <https://docs.onap.org/projects/onap-policy-parent/en/guilin/installation/oom.html#installing-or-upgrading-policy>`__ section for appropriate procedures.
Known Vulnerabilities
~~~~~~~~~~~~~~~~~~~~~
@@ -476,14 +476,14 @@ POLICY-APEX-PDP
* Passing parameters from ApexConfig to policy logic.
- TaskParameters can be used to pass parameters from ApexConfig to the policy logic. Consider a scenario where from CLAMP, serviceId or closedLoopId has to be passed to the policy, and this should be available to perform some logic or action within the policy. In the CLAMP UI, while configuring the APEX Policy, specifying taskParameters with these will enable this.
- - More information about the usage of Task Parameters can be found here: https://onap.readthedocs.io/en/latest/submodules/policy/parent.git/docs/apex/APEX-User-Manual.html#configure-task-parameters
+ - More information about the usage of Task Parameters can be found here: https://docs.onap.org/projects/onap-policy-parent/en/frankfurt/apex/APEX-User-Manual.html#configure-task-parameters
- In the taskLogic, taskParameters can be accessed as executor.parameters.get("ParameterKey1"))
- - More information can be found here: https://onap.readthedocs.io/en/latest/submodules/policy/parent.git/docs/apex/APEX-Policy-Guide.html#accessing-taskparameters
+ - More information can be found here: https://docs.onap.org/projects/onap-policy-parent/en/frankfurt/apex/APEX-Policy-Guide.html#accessing-taskparameters
* GRPC support for APEX-CDS interaction.
- - APEX-PDP now supports interaction with CDS over gRPC. Up through El Alto, CDS interaction was possible over REST only. A new plugin was developed in APEX for this feature. Refer the link for more details. https://onap.readthedocs.io/en/latest/submodules/policy/parent.git/docs/apex/APEX-User-Manual.html#grpc-io
+ - APEX-PDP now supports interaction with CDS over gRPC. Up through El Alto, CDS interaction was possible over REST only. A new plugin was developed in APEX for this feature. Refer the link for more details. https://docs.onap.org/projects/onap-policy-parent/en/frankfurt/apex/APEX-User-Manual.html#grpc-io
POLICY-XACML-PDP
================
@@ -530,7 +530,7 @@ System Limitations
The policy API component requires a fresh new database when migrating to the frankfurt release.
Therefore, upgrades require a fresh new database installation.
Please see the
-`Installing or Upgrading Policy <https://onap.readthedocs.io/en/frankfurt/submodules/policy/parent.git/docs/installation/oom.html#installing-or-upgrading-policy>`__ section for appropriate procedures.
+`Installing or Upgrading Policy <https://docs.onap.org/projects/onap-policy-parent/en/frankfurt/installation/oom.html#installing-or-upgrading-policy>`__ section for appropriate procedures.
Known Vulnerabilities
~~~~~~~~~~~~~~~~~~~~~