ansible-junos-stdlib
ansible-junos-stdlib copied to clipboard
Juniper
Junos modules for Ansible
junos_install_config has a timeout parameter but it's not used when opening the initial connection to the device, [here](https://github.com/Juniper/ansible-junos-stdlib/blob/master/library/junos_install_config#L211). If the device is down or the host/port is incorrect, it can...
The get_facts on a secondary node of a SRX Cluster displays the serialnumber of the primary node. the playbook: ``` - name: Deploy Cluster hosts: PROV gather_facts: no connection: local...
Enhancement request: Please provide a way to run BSD shell commands from Ansible playbooks. Using PyEZ we can do this from the StartShell module: ``` from jnpr.junos import Device from...
Issue Type ------ - Feature Idea Module Name ------ juniper_junos_command Summary ------ ansible core module junos_command has nice operational states validation capabilities leveraging junos xml and json representation. Here's an...
Issue Type ------ - Bug Report Module Name ------ juniper_junos_software ``` ansible 2.4.2.0 config file = /etc/ansible/ansible.cfg configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible...
Not having access to the file parameters on the jsnapy snap and check functions precludes having a test comparison against a "golden" test result, or creating a baseline test result....
Issue Type ------ - Bug Report Module Name ------ - paramiko ``` % pip3 freeze bcrypt==4.0.0 cffi==1.15.1 cryptography==38.0.1 Jinja2==3.1.2 junos-eznc==2.6.5 jxmlease==1.0.3 lxml==4.9.1 MarkupSafe==2.1.1 ncclient==0.6.13 netaddr==0.8.0 paramiko==2.11.0 pycparser==2.21 PyNaCl==1.5.0 pyparsing==3.0.9 pyserial==3.5...
Introduced "commit_sync" and "commit_force_sync" under juniper.device.config module ``` - name: "Confirm the commit with a commit check" juniper.device.config: check: true diff: false comment: "Juniper Network" commit_force_sync: True register: response ```...
It seems that the even though a default value is defined, it is now expected to be explicitly listed in the options. Fixes the following warning message: `[WARNING]: The "ansible_collections.juniper.device.plugins.connection.pyez"...
