Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retire Repo #246

Open
jvanderaa opened this issue Sep 30, 2020 · 2 comments
Open

Retire Repo #246

jvanderaa opened this issue Sep 30, 2020 · 2 comments

Comments

@jvanderaa
Copy link

ISSUE TYPE

  • Documentation Report

ANSIBLE VERSION

N/A

Network OS

N/A

SUMMARY

It looks as though the functionality from this has migrated its way into the modern network libraries within Ansible. This should be documented on the repository and also on Ansible Galaxy to shift and guide to the proper location for parsing specifically.

@epicanthal
Copy link

I am currently using the 'CLI Parser Directives' functionality which seems to not work any longer when moving to Ansible 2.10.x. So what @jvanderaa is saying is that Network CLI Filters is now the preferred method?

I am receiving the following error:

ERROR! Unexpected Exception, this is probably a bug: No module named 'ansible.module_utils.network_common'

Here are the sample tasks to reproduce:

  tasks:
    - name: Gather current running config via ios_facts module
      cisco.ios.ios_facts:
        gather_subset:
          - config

    - name: Import the network-engine role
      import_role:
        name: ansible-network.network-engine

    - name: Parse running-config
      command_parser:
        file: my_parser.yml
        content: "{{ ansible_net_config }}"

@jvanderaa
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants