Currently, replace assumes that the new group that is given is a
fully-formed object. But mpath groups really only have one attribute, and
that is the constituent next hop configuration. This may not be universally
true. From the usability perspective, it is desirable to allow the replace
operation
On 3/10/21 8:02 AM, Petr Machata wrote:
> Currently, replace assumes that the new group that is given is a
> fully-formed object. But mpath groups really only have one attribute, and
> that is the constituent next hop configuration. This may not be universally
> true. From the usability perspective
