summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorChris Dent <cdent@anticdent.org>2016-01-31 02:05:40 +0000
committerChris Dent <cdent@anticdent.org>2016-02-06 13:21:56 +0000
commitdc22e9fd30ea678edaf0a3237ed10c49128e87d9 (patch)
treed4148e6a29cb87ec76aa0ea8285c8225b17ed9d9 /releasenotes
parent410b123eedc9954a9736cf4d9da27919ff93d963 (diff)
downloadkeystonemiddleware-dc22e9fd30ea678edaf0a3237ed10c49128e87d9.tar.gz
Remove clobbering of passed oslo_config_config
Calling a ConfigOpts instance with new args will implicitly reset the config values in the instance. This means that in the previous revision of the code, any assignment of oslo_config_config to self._local_oslo_config would be instantly clobbered by calling self._local_oslo_config() to read from default_config_files. Now, if oslo_config_config is set to a non-None value it will be left unmolested. This is useful because oslo_config_config turns out to be the ideal way to pass config to AuthProtocol when the caller already has access to the project config object and neither global conf nor paste is being used. Change-Id: I0beb809bc5ace609561f10dc52800a8a6e03f7e6 Closes-Bug: #1540022
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/authprotocol-accepts-oslo-config-config-a37212b60f58e154.yaml10
1 files changed, 10 insertions, 0 deletions
diff --git a/releasenotes/notes/authprotocol-accepts-oslo-config-config-a37212b60f58e154.yaml b/releasenotes/notes/authprotocol-accepts-oslo-config-config-a37212b60f58e154.yaml
new file mode 100644
index 0000000..c844833
--- /dev/null
+++ b/releasenotes/notes/authprotocol-accepts-oslo-config-config-a37212b60f58e154.yaml
@@ -0,0 +1,10 @@
+---
+features:
+ - >
+ [`bug 1540022 <https://bugs.launchpad.net/keystonemiddleware/+bug/1540022>`_]
+ The auth_token middleware will now accept a conf setting named
+ ``oslo_config_config``. If this is set its value must be an existing
+ oslo_config `ConfigOpts`. ``olso_config_config`` takes precedence over
+ ``oslo_config_project``. This feature is useful to applications that
+ are instantiating the auth_token middleware themselves and wish to
+ use an existing configuration.