8c48341169
This change introduces a new option to define the region to which the Barbican endpoint belongs. This is required if the deployment has multiple regions and a single Keystone instance stores multiple Barbican endpoints for different regions. This change also ensures that the same interface and region are used in endpoint detection and api version detection. Change-Id: If2c0055d45922937e259a8f22f5879c9faa41e35 |
||
---|---|---|
.. | ||
add-to-dict-and-from-dict-conversions-to-managed-objects-95a9f0fdbd371a87.yaml | ||
add-vault-provider-29a4c19fe67ab51f.yaml | ||
bug-1876102-7c7288fb6e90b11d.yaml | ||
deprecate-auth-endpoint-b91a3e67b5c7263f.yaml | ||
drop-python-2-7-73d3113c69d724d6.yaml | ||
fix-vault-create-key-b4340a3067cbd93c.yaml | ||
fix-vault-flaky-kv-api-version-b0cd9d62a39d2907.yaml | ||
implements-keymanager-option-discovery-13a46c1dfc036a3f.yaml | ||
support-legacy-fixed-key-id-9fa897b547111610.yaml | ||
use-barbican-endpoint-type-config-option-e583d30930cc22ba.yaml | ||
use-barbican-region-name-config-option-31bec809292302b8.yaml | ||
vault-approle-support-5ea04daea07a152f.yaml | ||
vault-kv-mountpoint-919eb547764a0c74.yaml |