You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 modulecisco.ios.ios_facts:
gather_subset:
- config
- name: Import the network-engine roleimport_role:
name: ansible-network.network-engine
- name: Parse running-configcommand_parser:
file: my_parser.ymlcontent: "{{ ansible_net_config }}"
ISSUE TYPE
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.
The text was updated successfully, but these errors were encountered: