Ran
|
Jobs
1
|
Files
0
|
Run time
1s
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
<a href="https://github.com/napalm-automation/napalm/commit/<a class=hub.com/napalm-automation/napalm/commit/e4955be48e627720e410b2e7343ad3ea3c092634">e4955be48<a href="https://github.com/napalm-automation/napalm/commit/e4955be48e627720e410b2e7343ad3ea3c092634">">Use aply-groups inheritance on get-configuration RPC calls The behaviour for get-configuration RPC calls has been changed in 2af90cc75, in order to ensure we&#39;re gathering from the right database. The way junos-eznc works is that if there aren&#39;t any specific options passed in, it uses apply-groups by default. But when there are options passed in, as we do starting with 2af90cc75, it doesn&#39;t default the values of `inherit` and `groups`, and therefore when gathering the config it won&#39;t expand the apply-groups, see https://github.com/Juniper/py-junos-eznc/blob/</a><a class="double-link" href="https://github.com/napalm-automation/napalm/commit/<a class="double-link" href="https://github.com/napalm-automation/napalm/commit/ab0e8603eac56fa1d049695c7ef86eb64582ab8f">ab0e8603e</a>">ab0e8603e</a><a href="https://github.com/napalm-automation/napalm/commit/e4955be48e627720e410b2e7343ad3ea3c092634">/lib/jnpr/junos/factory/cfgtable.py#L517-L520. Changing this now, by adding a few new optional arguments, which allow the user to select the desired behaviour.
0 of 0 relevant lines covered (NaN%)
0.0 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
2 | 3403.2 (TOXENV=pylama) | 0 |
0.0 |
Travis Job 3403.2 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|