Importing a Firewall section shows applied_to = LogicalRouter

[fdhex]

As written in title I have imported a firewall section by id. It is an edge firewall on a T0
From my tfstate:

 "nsxt_firewall_section.section_prod": {
                    "type": "nsxt_firewall_section",
                    "depends_on": [],
                    "primary": {
                        "id": "ewadwadwa",
                        "attributes": {
                            "applied_to.#": "1",
                            "applied_to.903722171.is_valid": "true",
                            "applied_to.903722171.target_display_name": "my_to",
                            "applied_to.903722171.target_id": "dwadwadwad",
                            "applied_to.903722171.target_type": "LogicalRouter",
                            "description": "",
                            "display_name": "Infrastructure",
                            "id": "dwadwadwadwad",
                            "is_default": "false",
                            "revision": "2", [...]

But as written in docs, target_type LogicalRouter does not seem supported, so if in my resource I do write

resource "nsxt_firewall_section" "section_prod" {
    section_type = "LAYER3"
    stateful = "true"
    applied_to = {
        target_id = "dwadwadwad",
        target_type = "LogicalRouter"
    }
}

it fails and tells me LogicalRouter is not supported. Am I missing something?

Curl'ing the API /firewall/sections it mixes DFW and EFW rules, so I would assume EFW could be created using the same framework.

EDIT: I was able to make it work by adding LogicalRouter to the array at https://github.com/terraform-providers/terraform-provider-nsxt/blob/master/nsxt/resource_nsxt_firewall_section.go#L103 - the API behind is the same so it's only a matter of internal validation.

[fdhex]

Proposal in https://github.com/terraform-providers/terraform-provider-nsxt/pull/157