From 7bb701c74283fd54a3c66dd4852087fea6d55592 Mon Sep 17 00:00:00 2001 From: Ben Nemec Date: Fri, 22 Mar 2019 17:22:41 +0000 Subject: [PATCH] Clarify intended use case for oslo.config environment driver The original cycle highlight for this feature mentioned what it does but not how it was intended to be used. Change-Id: I68b380c89f97919c4a1c39df4107057120d0571e --- deliverables/stein/oslo.config.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/deliverables/stein/oslo.config.yaml b/deliverables/stein/oslo.config.yaml index 988d8edc59..36edaa2f32 100644 --- a/deliverables/stein/oslo.config.yaml +++ b/deliverables/stein/oslo.config.yaml @@ -11,8 +11,9 @@ cycle-highlights: on-disk config files to any Castellan-compatible keystore. This driver lives in the Castellan project, so Castellan must be installed in order to use it. - - Added a config driver to read config values from environment variables. - This driver is enabled by default in oslo.config. + - Added a config driver to read values from environment variables, which + allows configuration of services in containers without needing to + inject a file. This driver is enabled by default in oslo.config. - Added a config validation tool, ``oslo-config-validator``. This uses the oslo-config-generator data to find options in a config file that are not defined in the service.