Conversion of LTM policy fails silently

[gomesjj]

Hi,

F5 ACC Chariot v1.21.0 (VSCode)

I am trying to convert the configuration of a VIP, but the LTM policy fails without an error (the rest of the configuration coverts fine). The section of the configuration file is:

ltm policy /Common/INT-STG-AWS {
    controls { forwarding }
    requires { http client-ssl }
    rules {
        "Allow" {
            actions {
                0 {
                    forward
                    select
                    virtual /Common/BLUE-DGA-INT-AWS-STG-PPE_443_VS
                }
            }
            conditions {
                0 {
                    ssl-extension
                    ssl-client-hello
                    server-name
                    values { stage-pcs-service1.com cert-service1.com stage-service2.com stage-service3.com stage-service4.com stage-service5.com stage-service6.com }
                }
            }
        }
        "Drop" {
            actions {
                0 {
                    shutdown
                    connection
                }
            }
            conditions {
                0 {
                    ssl-extension
                    ssl-client-hello
                    server-name
                    not
                    values { stage-pcs-service1.com cert-service1.com stage-service2.com stage-service3.com stage-service4.com stage-service5.com stage-service6.com }
                }
            }
            ordinal 1
        }
    }
    strategy /Common/first-match
}

At first I thought the issue was related to the server-name values (multiple), but even if I try with a single one the conversion fails.

[DumpySquare]

Hi @gomesjj. Thank you for opening this issue. Unfortunately, this project only wraps the core ACC engine for use in vscode. I suggest you ping that project for feedback.

https://github.com/f5devcentral/f5-automation-config-converter