Takashi Kajinami 9575a24796 Query endpoint id from keystone ... Endpoint id is not predictable so users can't configure the endpoint_id option until keystone endpoints are created. This requires redundant steps in deployment. For example both keystone and glance are run by httpd + mod_wsgi then you first have to deploy keystone and then create glance endpoints, until you can install glance and restart httpd. This introduces a few new options to look up the target endpoint from Keystone. All these options accept predictable values. Closes-bug: #1931875 Change-Id: I0411d4aa6abd86cb38bf3c1999f2bae213983078		2024-09-05 11:08:12 +09:00
..
bug-1962406-e239d60400c726c8.yaml	oslo-config-generator: Fix ValueError	2022-02-28 01:27:50 +09:00
drop-python27-support-7c1d29f348060147.yaml	[ussuri][goal] Drop python 2.7 support and testing	2020-02-06 10:24:15 +01:00
enforcer-limit-caching-fb59725aad88b039.yaml	Add caching of limits in Enforcer	2021-10-18 21:43:57 +00:00
look-up-endpoint-id-from-keystone-9d8419673902c258.yaml	Query endpoint id from keystone	2024-09-05 11:08:12 +09:00
pre-stable-version-warning-83dbfc9427a22725.yaml	oslo.limit mistakenly released as 1.0.0 (release note)	2020-02-21 10:34:02 +01:00