security_nat_proxy-arp_interface_address/

README

This Folder is a sample implementation of configuring the below configuration on device using jtaf and terraform.

set security nat proxy-arp interface ge-0/0/0.0 address 10.0.0.40/32 to 10.0.0.43/32
set security nat proxy-arp interface ge-0/0/0.0 address 10.10.0.64/27
set security nat proxy-arp interface ge-0/0/0.0 address 10.1.1.23/24
set security nat proxy-arp interface ge-0/0/1.0 address 10.0.0.17/24

Details -

• module_file/xpath_sample.xml - The file has xpath used to generate the terraform provider
• module_file/resource_SecurityNatProxy__ArpInterfaceAddressToIpaddr.go - the generated module.
• module_file/junos-es-conf-security@2019-01-01.yang - the yang file used to generate the module.
• module_file/temp.toml -> the config file created to pass as argument to processYang and processProviders
• test.tf - The file has api written to set the configuration.
• terraform-provider-junos-device -> the generated binary

Understanding the implementation

1. processYang generates yin file and xpath using temp.toml. Related xpath for this configuration will be /security/nat/proxy-arp/interface/address/to/ipaddr which can be found with help of generated xpath file. Refer link
2. processProviders generates module using temp.toml. Refer link
3. terraform provider is generated. Refer link
4. Copy the generated provider and initialize it via terraform init api.
5. create a testfile for execution. test.tf is the sample file used.

How test.tf is written

• We refer the generated modules for its creation. resource_SecurityNatProxy__ArpInterfaceAddressToIpaddr.go is to be referred in this example.
• The hierarchy used for the module generation is /security/nat/proxy-arp/interface/address/to/ipaddr as mentioned in xpath_sample.xml file.
• xmlSecurityNatProxy__ArpInterfaceAddressToIpaddr in the generated module gives the xml hierarchy as seen in the device.
• junosSecurityNatProxy__ArpInterfaceAddressToIpaddr in the generated module provides the list of variables to be used to set the configuration. The variables may have duplicate names with incremental numbers attached at the end. The description of each variable provides their exact hierarchy which helps user to relate the variable to the xml schema.
• The container or list names are not required to be mentioned in the test.tf file.
• The key for each list also needs to be mentioned while setting a sub-element as it is required to translate to correct configuration. In this example we have two lists interface and address in the hierarchy /security/nat/proxy-arp/interface/address/to/ipaddr. name is the variable assigned to both of its key element and they are differentiated by integers at the end and it needs to be mentioned in the test.tf
• The variable ipaddr is assigned to leaf-element ipaddr and needs to be mentioned in the test.tf .
• The variable resource_name helps to identify if it is a group based configuration and is required.