f91aec5869
Add microversion 3.64 for including the encryption_key_id in the volume and backup details when the associated volume is encrypted. This facilitates associating encryption keys (typically stored in Barbican) with the volume or backup that uses it. The encryption_key_id is included in the details only when the associated volume is encrypted, and it isn't using the all-zeros key ID used by the legacy fixed-key ConfKeyMgr. APIImpact DocImpact Implements: blueprint include-encryption-key-id-in-details Change-Id: I16f54e6722cdbcbad4af1eb0d30264b0039412fd
7 lines
207 B
YAML
7 lines
207 B
YAML
---
|
|
features:
|
|
- |
|
|
Starting with API microversion 3.64, an ``encryption_key_id`` attribute
|
|
is included in the response body of volume and backup details when the
|
|
associated volume is encrypted.
|