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
..
tests	Query endpoint id from keystone	2024-09-05 11:08:12 +09:00
__init__.py	Init repo	2018-05-17 18:06:06 +08:00
_i18n.py	ADD i18n file	2018-07-30 16:15:03 +08:00
exception.py	Add flat enforcer	2019-11-25 18:30:28 +00:00
fixture.py	Add caching of limits in Enforcer	2021-10-18 21:43:57 +00:00
limit.py	Query endpoint id from keystone	2024-09-05 11:08:12 +09:00
opts.py	Query endpoint id from keystone	2024-09-05 11:08:12 +09:00