napalm_get_config module to fetch device configurations #193
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing NAPALM driver get_config method
anirudhkamath
force-pushed
the
napalm_get_config-module
branch
from
2ddeb8e to
485d09d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new Ansible module, named
napalm_get_configto allow playbooks to fetch device configurations using their platform specific NAPALM driverget_configmethod.The module supports the same base options as other NAPALM modules: hostname, username, password, dev_os, provider, timeout, and optional_args, along with 3 other options which are used in the
get_configNAPALM method:and returns back the dict output containing running, startup, and candidate configurations in the result. Example of usage is included in the module docstrings