diff --git a/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po b/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po index 5b8a4ff75..da8ed5415 100644 --- a/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po +++ b/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po @@ -10,11 +10,11 @@ msgid "" msgstr "" "Project-Id-Version: Barbican Release Notes\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-17 15:31+0000\n" +"POT-Creation-Date: 2024-08-27 18:34+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"PO-Revision-Date: 2024-07-10 12:13+0000\n" +"PO-Revision-Date: 2024-09-04 09:49+0000\n" "Last-Translator: Andi Chandler \n" "Language-Team: English (United Kingdom)\n" "Language: en_GB\n" @@ -51,6 +51,9 @@ msgstr "11.0.0-24" msgid "12.0.0" msgstr "12.0.0" +msgid "12.0.0.0rc1" +msgstr "12.0.0.0rc1" + msgid "12.0.1" msgstr "12.0.1" @@ -72,8 +75,8 @@ msgstr "17.0.0" msgid "18.0.0" msgstr "18.0.0" -msgid "18.0.0-15" -msgstr "18.0.0-15" +msgid "18.0.0-20" +msgstr "18.0.0-20" msgid "2.0.0" msgstr "2.0.0" @@ -349,6 +352,15 @@ msgstr "" "Fixed Story 2009664 - Fixed the Consumer controller to be able to use the " "associated Container's ownership information in policy checks." +msgid "" +"Fixed the response code for invalid subroutes for individual secrets. The " +"API was previously responding with the incorrect code \"405 - Method not " +"allowed\", but now responds correctly with \"404 - Not Found\"." +msgstr "" +"Fixed the response code for invalid subroutes for individual secrets. The " +"API was previously responding with the incorrect code \"405 - Method not " +"allowed\", but now responds correctly with \"404 - Not Found\"." + msgid "" "Fixed the response code for invalid subroutes for individual secrets. The " "API was previously responding with the incorrect code \"406 - Method not " @@ -445,6 +457,29 @@ msgstr "Mitaka Series Release Notes" msgid "New Features" msgstr "New Features" +msgid "" +"New feature to support multiple secret store plugin backends. This feature " +"is not enabled by default. To use this feature, the relevant feature flag " +"needs to be enabled and supporting configuration needs to be added in the " +"service configuration. Once enabled, a project administrator will be able to " +"specify one of the available secret store backends as a preferred secret " +"store for their project secrets. This secret store preference applies only " +"to new secrets (key material) created or stored within that project. " +"Existing secrets are not impacted. See http://docs.openstack.org/developer/" +"barbican/setup/plugin_backends.html for instructions on how to setup " +"Barbican multiple backends, and the API documentation for further details." +msgstr "" +"New feature to support multiple secret store plugin backends. This feature " +"is not enabled by default. To use this feature, the relevant feature flag " +"needs to be enabled and supporting configuration needs to be added in the " +"service configuration. Once enabled, a project administrator will be able to " +"specify one of the available secret store backends as a preferred secret " +"store for their project secrets. This secret store preference applies only " +"to new secrets (key material) created or stored within that project. " +"Existing secrets are not impacted. See http://docs.openstack.org/developer/" +"barbican/setup/plugin_backends.html for instructions on how to setup " +"Barbican multiple backends, and the API documentation for further details." + msgid "" "New feature to support multiple secret store plugin backends. This feature " "is not enabled by default. To use this feature, the relevant feature flag " @@ -487,6 +522,17 @@ msgstr "" "Now Barbican uses oslo.db for database connection. The features implemented " "in oslo.db can be now leveraged in Barbican." +msgid "" +"Now within a single deployment, multiple secret store plugin backends can be " +"configured and used. With this change, a project administrator can pre-" +"define a preferred plugin backend for storing their secrets. New APIs are " +"added to manage this project level secret store preference." +msgstr "" +"Now within a single deployment, multiple secret store plugin backends can be " +"configured and used. With this change, a project administrator can pre-" +"define a preferred plugin backend for storing their secrets. New APIs are " +"added to manage this project level secret store preference." + msgid "" "Now within a single deployment, multiple secret store plugin backends can be " "configured and used. With this change, a project adminstrator can pre-define "