Deprecate the `vendordata_driver` config option.
This allowed creating a differ class loader for defining vendordata metadata for the metadata server. The default driver loads from a json file that can be arbitrarily specified, so is still quite flexible. Change-Id: I0f9866320cd655134281193c50ec170ea20c011a
This commit is contained in:
@@ -50,7 +50,8 @@ metadata_opts = [
|
|||||||
'config drive'),
|
'config drive'),
|
||||||
cfg.StrOpt('vendordata_driver',
|
cfg.StrOpt('vendordata_driver',
|
||||||
default='nova.api.metadata.vendordata_json.JsonFileVendorData',
|
default='nova.api.metadata.vendordata_json.JsonFileVendorData',
|
||||||
help='Driver to use for vendor data'),
|
help='DEPRECATED: Driver to use for vendor data',
|
||||||
|
deprecated_for_removal=True),
|
||||||
]
|
]
|
||||||
|
|
||||||
CONF = cfg.CONF
|
CONF = cfg.CONF
|
||||||
|
|||||||
@@ -0,0 +1,10 @@
|
|||||||
|
---
|
||||||
|
deprecations:
|
||||||
|
|
||||||
|
- Deprecate the ``vendordata_driver`` config option. This allowed
|
||||||
|
creating a different class loader for defining vendordata
|
||||||
|
metadata. The default driver loads from a json file that can be
|
||||||
|
arbitrarily specified, so is still quite flexible. Deployments that
|
||||||
|
felt the need to use this facility are encoraged to propose
|
||||||
|
additions upstream so we can create a stable and supported
|
||||||
|
interface here.
|
||||||
Reference in New Issue
Block a user