9575a24796
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
12 lines
338 B
YAML
12 lines
338 B
YAML
---
|
|
features:
|
|
- |
|
|
The following options have been added to the ``[oslo_limit]`` section.
|
|
When these options are set instead of the ``endpoint_id`` option, endpoint
|
|
id is looked up from keystone API.
|
|
|
|
- ``endpoint_service_name``
|
|
- ``endpoint_service_type``
|
|
- ``endpoint_region_name``
|
|
- ``endpoint_interface``
|