Deprecate the "metadata_encryption_key" option

Change-Id: I15d388793f12ad8305095b0993a4e70d1bea6851
This commit is contained in:
Pranali Deore
2024-07-02 08:16:16 +00:00
parent 4dec531b0a
commit 006ef41c0b
2 changed files with 25 additions and 0 deletions

View File

@@ -475,6 +475,16 @@ Related options:
""")),
cfg.StrOpt('metadata_encryption_key',
deprecated_for_removal=True,
deprecated_since="Dalmatian",
deprecated_reason=_("""
This option doesnt serves the purpose of encryption of location metadata,
whereas it encrypts location url only for specific APIs. Also if enabled
this during an upgrade may disrupt existing deployments, as it does not
support/provide db upgrade script to encrypt existing location URLs.
Moreover, its functionality for encrypting location URLs is inconsistent
which is resulting in download failures.
"""),
secret=True,
help=_("""
AES key for encrypting store location metadata.

View File

@@ -0,0 +1,15 @@
---
deprecations:
- |
The Glance API configuration options ``metadata_encryption_key`` is
deprecated in this release and is subject to removal at the beginning
of the `F` (2025.2) development cycle.
The `metadata_encryption_key` and it's related functioanlity don't
serve the purpose of encryption of location metadata, whereas it encrypts
location url only for specific APIs. Also if enabled this during an
upgrade, may disrupt existing deployments, as it does not support/provide
db upgrade script to encrypt existing location URLs. Moreover, its
functionality for encrypting location URLs is inconsistent which
resulting in download failures.