Issue with parsing a list of unnamed maps in ltm profile fix

[jszczepanskif5]

Environment

• Application Services Version: 1.14.0
• BIG-IP Version: N/A

Summary

Currently in a spot where config contains a list of unnamed maps as shown below, only the last one is being added in the output as3 declaration. I currently know of only one as3-supported field formatted like this - in ltm profile fix; unsure if there are any other.

Steps To Reproduce

Steps to reproduce the behavior:

1. Convert following config:

ltm profile fix /datagroups/application_1/profileFIXcustom {
    app-service none
    defaults-from /Common/fix
    description none
    error-action drop-connection
    full-logon-parsing false
    message-log-publisher /Common/local-db-publisher
    quick-parsing true
    report-log-publisher /Common/local-db-publisher
    response-parsing true
    sender-tag-class {
        {
            sender-id RefInternalDG
            tag-map-class /Common/dataGroupRefInternal
        }
        {
            sender-id RefExternalDG
            tag-map-class /Common/dataGroupRefExternal
        }
    }
    statistics-sample-interval 45
}

2. Observe the following output

{
    "class": "ADC",
    "schemaVersion": "3.29.0",
    "id": "urn:uuid:2fe3e5cd-cde9-4558-9480-8387f6fa9950",
    "label": "Converted Declaration",
    "remark": "Auto-generated by AS3 Config Converter",
    "datagroups": {
        "class": "Tenant",
        "application_1": {
            "class": "Application",
            "template": "generic",
            "profileFIXcustom": {
                "parentProfile": {
                    "bigip": "/Common/fix"
                },
                "remark": "none",
                "errorAction": "drop-connection",
                "fullLogonParsingEnabled": false,
                "messageLogPublisher": {
                    "bigip": "/Common/local-db-publisher"
                },
                "quickParsingEnabled": true,
                "reportLogPublisher": {
                    "bigip": "/Common/local-db-publisher"
                },
                "responseParsingEnabled": true,
                "senderTagMappingList": [
                    {
                        "senderId": "RefExternalDG",
                        "tagDataGroup": {
                            "use": "/Common/Shared/dataGroupRefExternal"
                        }
                    }
                ],
                "statisticsSampleInterval": 45,
                "class": "FIX_Profile"
            }
        }
    }
}

Notice how the SenderTagMappingList field contains only one entry.

Expected Behavior

SenderTagMappingList should include references to both data groups.

<...>
                "senderTagMappingList": [
                    {
                        "senderId": "RefInternalDG",
                        "tagDataGroup": {
                            "use": "/Common/Shared/dataGroupRefInternal"
                        }
                    },
                    {
                        "senderId": "RefExternalDG",
                        "tagDataGroup": {
                            "use": "/Common/Shared/dataGroupRefExternal"
                        }
                    }
                ],
<...>

Actual Behavior

Only one key is included as shown in the example above above.

Note how in the 'recognized' (parsed?) config json returned via the api, only one field is present as well:

<...>
    "recognized": {
        "ltm profile fix /tenant_1/application_1/profileFIXcustom": {
            "app-service": "none",
            "defaults-from": "/Common/fix",
            "description": "none",
            "error-action": "drop-connection",
            "full-logon-parsing": "false",
            "message-log-publisher": "/Common/local-db-publisher",
            "quick-parsing": "true",
            "report-log-publisher": "/Common/local-db-publisher",
            "response-parsing": "true",
            "sender-tag-class": {
                "": {
                    "sender-id": "RefExternalDG",
                    "tag-map-class": "/tenant_1/application_1/dataGroupRefExternal"
                }
            },
            "statistics-sample-interval": "45"
        },
    }
<...>

Likely just an issue with the parser overwriting 'duplicate' empty keys in the sender-tag-class collection.

[mdditt2000]

Create internal issue CHARON-450 for PM tracking.

[mdditt2000]

Resolved