ca27736810
I suppose that methods get_resource_manager_extra_kwargs and add_resource_manager_extra_kwargs_hook were designed in those days when Nova API had extensions. Nowdays, Nova API has strict schema validation of requests, so no additional arguments are allowed and these methods look redundant. The fact that get_resource_manager_extra_kwargs lists of the objects added by add_resource_manager_extra_kwargs_hook whereas add_resource_manager_extra_kwargs_hook is not called anywhere doesn't add chances for leaving these methods in our code. Compatibility: both methods are designed for CLI and the CLI behaviour will not change after removing them, so we can do a cleanup without following standard deprecation cycle. Change-Id: Id61457c3db8a17e2294dc579b2519873927fec48
11 lines
505 B
YAML
11 lines
505 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
``novaclient.utils.add_resource_manager_extra_kwargs_hook`` and
|
|
``novaclient.utils.get_resource_manager_extra_kwargs`` were designed for
|
|
supporting extensions in nova/novaclient. Nowadays, this "extensions"
|
|
feature is abandoned and both ``add_resource_manager_extra_kwargs_hook``,
|
|
``add_resource_manager_extra_kwargs_hook`` are not used in novaclient's
|
|
code. These methods are not documented, so we are removing them without
|
|
standard deprecation cycle.
|