Playbook fails on existing configuration about ansible-junos-stdlib HOT 5 CLOSED

Access ports can only have 1 VLAN assigned to them (as you know), so you will need to delete the vlan assignment before you push the config. It acts the same as if you were on the cmd line.
I would just add that to the Configuration File in your example, so it deletes the vlan stanza and then adds in the stanza that you want. I haven't tested this but it should be something similar to the following:

interfaces {
    ge-0/0/7 {
        description TEST;
        unit 0 {
            family ethernet-switching {
                port-mode access;
                delete: vlan; 
                vlan {
                    members VL0002;
                }
            }
        }
    }
}

This would be easier with the set command if you want to go that route.

from ansible-junos-stdlib.

Or use XML instead for your config format. It allows you to clearly specify which sections need to be merged, replaced or deleted. E.g.

<configuration>
  <interfaces>
      <name>ge-0/0/7</name>
          <description>TEST</description>
            <unit>
                <name>0</name>
                <family>
                    <ethernet-switching>
                        <port-mode>access</port-mode>
                        <vlan operation="replace">
                            <members>VL0002</members>
                        </vlan>
                    </ethernet-switching>
                </family>
            </unit>
      </interfaces>
</configuration>

XML has the added benefit of being more easily parsed, so you can do policy checks after your build all your configs.

from ansible-junos-stdlib.

Completely agree. Heck, for that matter even the set notation would be much easier, but the XML is the preferred method if you want to make it "smart"

from ansible-junos-stdlib.

Thanks I will give the XML a shot. I have previously tried using the
delete: vlan; statement with both the Ansible module and with a custom
python script using the junos-eznc module and neither worked (though it is
possible I did something wrong).

On Mon, Jun 15, 2015 at 12:01 PM, sdndude [email protected] wrote:

Completely agree. Heck, for that matter even the set notation would be
much easier, but the XML is the preferred method if you want to make it
"smart"

—
Reply to this email directly or view it on GitHub
#65 (comment)
.

from ansible-junos-stdlib.

Load Replace support provided by #71

from ansible-junos-stdlib.