
The filename was incorrectly implemented as network_info.json instead of network_data.json. Support for reading the correct file already exists in glean. As such, we need to write both files for user compatability in the short term, and remove the second file at a later point in time. A release note has been added detailing this as well. Co-Authored-By: Julia Kreger <juliaashleykreger@gmail.com> Change-Id: I4150f86fbc141dcd6fd12094acab1ca43d76910c
18 lines
793 B
YAML
18 lines
793 B
YAML
---
|
|
deprecations:
|
|
- The ``node_network_info`` parameter has been deperecated
|
|
in favor for the ``node_network_data`` parameter as the
|
|
relaated configurtion drive ``network_info.json`` file was
|
|
misnamed origionally, and should have been named
|
|
``network_data.json``.
|
|
Support for the node_network_info, and the continued
|
|
write-out of the network_info.json file in configuration
|
|
drives will be removed in the Queens cycle.
|
|
fixes:
|
|
- When support for passing configuration drive data to the
|
|
nodes was originally created, the file was accidently named
|
|
incorrectly as ``network_info.json``. The correct filename
|
|
is ``network_data.json``. Both files will now be written
|
|
until support for writing ``network_info.json`` is removed
|
|
in the Queens cycle.
|