From 87b9c2b9168553b68fffbdc2f499469a61335993 Mon Sep 17 00:00:00 2001 From: Chris Dent Date: Mon, 5 Dec 2016 15:06:26 +0000 Subject: [PATCH] Update cors-to-versions-pipeline release note The release note added in I4052186bffa3bddb4d28e378e6a135694a71e05b was not entirely clear on what needs to be done to enable the feature in existing deployments. This change attempts to make things more clear. Change-Id: Iaa18c70b8536f01fb543cb2cf3d2e4144893b9cd --- .../add-cors-to-versions-pipeline-56277ca66e796569.yaml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/releasenotes/notes/add-cors-to-versions-pipeline-56277ca66e796569.yaml b/releasenotes/notes/add-cors-to-versions-pipeline-56277ca66e796569.yaml index 928c4a0ffcc1..3b520029e9ee 100644 --- a/releasenotes/notes/add-cors-to-versions-pipeline-56277ca66e796569.yaml +++ b/releasenotes/notes/add-cors-to-versions-pipeline-56277ca66e796569.yaml @@ -1,6 +1,7 @@ --- upgrade: - - CORS headers have been added to the versions REST API, in order - to support versions discovery. If using 'oscomputeversions' - pipeline in '/etc/nova/api-paste.ini', it is required to update the - pipeline to include 'cors' filter. + - To allow access to the versions REST API from diverse origins, + CORS support has been added to the 'oscomputeversions' pipeline + in '/etc/nova/api-paste.ini'. Existing deployments that wish to + enable support should add the 'cors' filter at the start of the + 'oscomputeversions' pipeline.