From a174cadc174377c9c38df860d7e37b5799067bc7 Mon Sep 17 00:00:00 2001 From: FrancescoFioraEst Date: Fri, 31 Mar 2023 10:56:02 +0100 Subject: [PATCH] Fix Anchor installing-or-upgrading-policy in docs Issue-ID: POLICY-4623 Change-Id: I714c79306c920aba861f65dd1b064c05f055ab4c Signed-off-by: FrancescoFioraEst --- docs/conf.yaml | 7 ------- docs/release-notes.rst | 4 ++-- 2 files changed, 2 insertions(+), 9 deletions(-) delete mode 100644 docs/conf.yaml diff --git a/docs/conf.yaml b/docs/conf.yaml deleted file mode 100644 index ab592813..00000000 --- a/docs/conf.yaml +++ /dev/null @@ -1,7 +0,0 @@ ---- -project_cfg: onap -project: onap - -# Change this to ReleaseBranchName to modify the header -default-version: latest -# diff --git a/docs/release-notes.rst b/docs/release-notes.rst index ce9720cc..cf257275 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -1374,7 +1374,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 `__ section for appropriate procedures. +`Installing or Upgrading Policy `__ section for appropriate procedures. Known Vulnerabilities ~~~~~~~~~~~~~~~~~~~~~ @@ -1679,7 +1679,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 `__ section for appropriate procedures. +`Installing or Upgrading Policy `__ section for appropriate procedures. Known Vulnerabilities ~~~~~~~~~~~~~~~~~~~~~ -- 2.16.6