The driver cannot replace a device's configuration and said so with a load_replace_candidate that raised NotImplementedError. A method that only raises still looks like a replace to anyone who asks whether the driver has one, so netOrk offered a config restore for these devices that could only fail.
load_replace_candidate = None is how a driver switches off a method (napalm-device-types' convention, which netOrk's capability checks follow), so asking now says no. Nothing in the driver or in netOrk calls it directly except netOrk's restore, which asks first.
test_load_replace_candidate_raises in tests/test_zyxel.py is replaced by the new test; the merge stub keeps its own test.
tests/test_config_replace.py (new, written first): the class has no callable load_replace_candidate.
README and CHANGELOG (Unreleased → Changed).
For NetOrk/netork#2503 (netOrk PR NetOrk/netork#2510).
The driver cannot replace a device's configuration and said so with a `load_replace_candidate` that raised `NotImplementedError`. A method that only raises still looks like a replace to anyone who asks whether the driver has one, so netOrk offered a config restore for these devices that could only fail.
`load_replace_candidate = None` is how a driver switches off a method (napalm-device-types' convention, which netOrk's capability checks follow), so asking now says no. Nothing in the driver or in netOrk calls it directly except netOrk's restore, which asks first.
`test_load_replace_candidate_raises` in `tests/test_zyxel.py` is replaced by the new test; the merge stub keeps its own test.
- `tests/test_config_replace.py` (new, written first): the class has no callable `load_replace_candidate`.
- README and CHANGELOG (Unreleased → Changed).
The driver cannot replace a device's configuration, and said so with a
load_replace_candidate that raised NotImplementedError. A method that only
raises still looks like a replace to anyone who asks whether the driver has
one: netOrk offered a config restore for these devices that could only fail.
None is how a driver switches off a method, the convention netOrk's
capability checks and napalm-device-types follow, so asking now says no.
Nothing in the driver calls it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For NetOrk/netork#2503 (netOrk PR NetOrk/netork#2510).
The driver cannot replace a device's configuration and said so with a
load_replace_candidatethat raisedNotImplementedError. A method that only raises still looks like a replace to anyone who asks whether the driver has one, so netOrk offered a config restore for these devices that could only fail.load_replace_candidate = Noneis how a driver switches off a method (napalm-device-types' convention, which netOrk's capability checks follow), so asking now says no. Nothing in the driver or in netOrk calls it directly except netOrk's restore, which asks first.test_load_replace_candidate_raisesintests/test_zyxel.pyis replaced by the new test; the merge stub keeps its own test.tests/test_config_replace.py(new, written first): the class has no callableload_replace_candidate.