bewing
bewing
Looks like https://pythonhosted.org/six/#six.reraise is needed for full compatibility between py2 and py3 for re-raising exceptions. Standalone code in https://stackoverflow.com/questions/34463087/raise-exception-in-python-2-x-and-3-x
What if there is an OPA Gatekeeper policy enforcing resource requests? The spec for the migration job should be editable
I believe all codepaths to client init are adjusted now.
Is there an actual deployment method where the first and last IPs are not usable? I would expect a more robust method of marking IPs as unusable if that were...
As an alternate explanation to this bug (it took me a minute to parse): `test_model` will print the first key whose type does not match annotation, plus all remaining tested...
If you install the `wheel` package first via pip, does `pip install napalm` succeed afterwards? Building `cryptography` from source requires quite the intensive build toolchain
Would be awesome if this could be generically available on other objects that support functions (networks, etc)
Can we add a SSH test double class to https://github.com/napalm-automation/napalm/blob/develop/test/eos/conftest.py and possibly start testing some of the differences in behavior between the SSH and eAPI transports/drivers/devices?
I also think `eos_ssh` folder makes more sense. I'll look at cribbing what's necessary from the existing _ssh folders and the standard EOS test double to arrange the boilerplate. @derekdainys...
Apologies for the delays. Tests look good, much thanks!