openstack-ansible-os_keystone/releasenotes/notes/git-sourced-config-change-5b445d3ce26d29c1.yaml
Jesse Pretorius 8367e44230 Use the venv contents instead of a git source for templates
When deploying the base templates for api-paste, policy files
and other files which are included in the service git source,
we now use the venv files instead of requiring access to a
git source and a complex set of lookups and variable
implementations.

This is simpler and more cross-series, and works from Queens
due to the related bug's patches.

Change-Id: I6a4e2514e66b15b2ae227e62b6dc9ae1a50a4fbd
Related-Bug: #1718356
2018-04-03 09:53:34 +01:00

18 lines
761 B
YAML

---
upgrade:
- |
In order to collect the default files used for various templates, the
implementation has been changed from using a git source to rather
using the built-in templates from the venv build based on the setup.cfg
file. As such, the following variables have been removed.
* ``keystone_git_config_lookup_location``
* ``keystone_paste_git_file_path``
* ``keystone_sso_callback_git_file_path``
Instead, a location on the deployment host where the venv defaults are
stored is now configurable using the variable
``keystone_config_cache_path`` which defaults to ``cache/keystone`` in
the deploy user home directory. This location is used as a template
source when deploying the file to the target host.