Binding port lists to virtual servers is not functional

[npmaslow]

Environment

• Application Services Version: 3.51.0
• BIG-IP Version: 17.1.1

Summary

Prior Issue 269 with bug AUTOTOOL-3881 indicated the desire to bind a Net_Port_List to the virtualPort parameter for a virtual server class Service_TCP for example. Usage of Firewall_Port_List requires AFM which seems to be a different path than simply creating a port list.

Steps To Reproduce

Steps to reproduce the behavior:

1. Here are the two objects in question:

               "pl_443-446": {
                   "class": "Net_Port_List",
                   "ports": [
                       443,
                       446
                   ]
               },
       "vs_test": {
         "class": "Service_TCP",
         "layer4": "tcp",
         "pool": "pool_test",
         "translateServerAddress": true,
         "translateServerPort": true,
         "profileTCP": {
           "ingress": {
             "use": "client_tcp_test"
           },
           "egress": {
             "use": "server_tcp_test"
           }
         },
         "shareAddresses": true,
         "virtualAddresses": [
           {
             "use": "/Common/Shared/va_test"
           }
         ],
         "virtualPort": {
           "bigip": "/Common/Shared/pl_443-446"
         },
         "persistenceMethods": []
       },

2. Observe the following error response:

   {
   "code": 422,
   "errors": [
       "/other/test/vs_test/virtualPort: should be integer"
   ],
   }

Expected Behavior

The port list should be able to be referenced under a virtual server service declaration.

Actual Behavior

The error indicated above.

[sunitharonan]

Thank you for reaching out. We have created a internal product backlog AUTOTOOL-4439 for this item, in order for us to prioritize please reach out to us at automation_toolchain_pm@f5.com