From 103801a9ad4b6bb3d9db1117a0cd49d09a1ade96 Mon Sep 17 00:00:00 2001 From: Ruby Loo Date: Thu, 2 Aug 2018 14:40:39 +0000 Subject: [PATCH] Update the reno for the reset_interfaces feature This updates the release note for the 'reset_interfaces' query parameter of a PATCH request to update a node. It clarifies that it is a query parameter and fixes some grammatical issues. Change-Id: I19a9e099ee4d5e9a6b4a6d49d851b5134aa02337 --- releasenotes/notes/reset-interface-e62036ac76b87486.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/releasenotes/notes/reset-interface-e62036ac76b87486.yaml b/releasenotes/notes/reset-interface-e62036ac76b87486.yaml index 77a1cf9595..cde885934b 100644 --- a/releasenotes/notes/reset-interface-e62036ac76b87486.yaml +++ b/releasenotes/notes/reset-interface-e62036ac76b87486.yaml @@ -2,6 +2,7 @@ features: - | Starting with API version 1.45, PATCH requests to ``/v1/nodes/`` - accept the new parameter ``reset_interfaces``. If can be provided whenever - the ``driver`` field is updated to reset all hardware interfaces to their - defaults, expect for ones updated in the same request. + accept the new query parameter ``reset_interfaces``. It can be provided + whenever the ``driver`` field is updated. If set to 'true', all hardware + interfaces wil be reset to their defaults, except for ones updated in the + same request.