Feature request: add forwarding-options evpn-vxlan resource

[NikitaPuglachenko]

Description

Could you add forwarding-options evpn-vxlan resource?

New or Affected Resource(s)

• junos_forwardingoptions_evpn_vxlan

Example Junos Configuration

[edit forwarding-options]
evpn-vxlan {
    gbp {
        ingress-enforcement;
        tag-only-policy;
    }
    host-originated-packets {
        gbp-src-tag gbp-src-tag;
    }
    reroute-address {
        inet address;
        inet6 address;
    }
    shared-tunnels;
    vxlan-trans-vni-enable;
 }

Potential Terraform Configuration

resource "junos_forwardingoptions_evpn_vxlan" "demo" {
  gbp {
    ingress_enforcement  = true | null
    tag_only_policy      = true | null
  }
  host_originated_packets {
    gbp_src_tag          = "gbp-src-tag"
  }
  reroute_address_inet   = true | null
  reroute_address_inetv6 = true | null
  shared_tunnels         = true | null
  vxlan_trans_vni_enable = true | null
}

References

https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/evpn-vxlan.html

[jeremmfr]

Hi 👋

Most options in forwarding-options evpn-vxlan seem recent, but unfortunately I don't have access to a recent version of Junos, with the lab I use, that will provide to validate the format of potential provider arguments to manage these options, detect potential conflict between these options, test the provider integration of the arguments.

The only option that access on my lab is shared-tunnels, is that the one you need ?

[NikitaPuglachenko]

Hi 👋

Most options in forwarding-options evpn-vxlan seem recent, but unfortunately I don't have access to a recent version of Junos, with the lab I use, that will provide to validate the format of potential provider arguments to manage these options, detect potential conflict between these options, test the provider integration of the arguments.

The only option that access on my lab is shared-tunnels, is that the one you need ?

Hi Jeremy 👋
Yes, that's fine for me. Many thanks!

[jeremmfr]

I'm reopening the issue, the new resource has not yet been integrated.