iapp::is VARNAME STRING STRING...

iapp::is ::net__route_to_bigip "yes"

iapp::substa ARRAYNAME

set do_snat      [expr { [iapp::is ::net__same_subnet  yes] \
                 || ![iapp::is ::net__route_to_bigip yes] || !$advanced}]
set do_automap   [expr { [iapp::is ::net__snat_type automap] || !$advanced}]
set new_snatpool [iapp::is ::net__snatpool $::CREATE_NEW_ANSWER]

# array keys: $do_snat,$do_automap,$new_snatpool
array set snatpool_arr {
    1,1,1 { snat automap }
    1,1,0 { snat automap }
    1,0,1 { snatpool [iapp::conf create ltm snatpool ${app}_snatpool \
            members replace-all-with \{ [string map \
            {"addr " "" \{ "" \} ""} $::net__snatpool_members] \} ]}
    1,0,0 { snatpool $::net__snatpool }
    *     { snat none }
}

set snat_action [iapp::substa snatpool_arr($do_snat,$do_automap,$new_snat)]

iapp::conf [create|modify|delete] ARGS

iapp::conf create ltm profile analytics ${app}_analytics \
     defaults-from analytics

iapp::make_safe_password STRING

iapp::conf modify ltm monitor http ${app}_monitor password \
    [iapp::make_safe_password $::monitor__passwd]

iapp::tmos_version COMPARATOR VALUE

set use_httpclass [iapp::tmos_version < 11.4]

iapp::get_items [OPTIONS] ARGS

-exists      returns 0 if query result is errored or empty, otherwise
             returns the number of query results.
-nocomplain  silently returns null if the query results in an error.
-list        formats the return value as a list. If not present, the
             return value is joined with \n as required in APL.
-norecursive overrides the default, which assumes all queries are recursive.
-local       performs the query in the iApp's local directory.
-dir         performs the query in a user-specified directory.
-filter      returns the subset of values that match the query spec.

set is_edge [expr { ![iapp::get_items -exists -norecursive \
    ltm persistence cookie /Common/cookie] }]

iapp::destination [OPTIONS] ADDR [PORT]

-mask         returns a mask instead of a destination
-length       specifies the mask using CIDR format (assumes -mask)
-route_domain appends a route domain (incompatible with -mask)

iapp::pool_members [OPTIONS] MEMBER_TABLE

-port         overrides the port numbers specified in the member table
-route_domain appends a route domain to each address
-aaa_domain   returns a configuration in aaa domain format
-aaa_pool     returns a configuration in aaa pool format
-fields       identifies the column values in the member table
              the default field mapping is:

              TMSH Parameter    Member Table Column
                address           addr
                port              port
                port-secure       port_secure
                connection-limit  connection_limit
                priority-group    priority
                ratio             ratio

iapp::debug ARGS

iapp::apm_config ARRAY_NAME

<ITEM> The object name, eg. apm_access
<PREFIX> The app name, including folder, eg. /Common/my_app.app/my_app

<PROFILE_TYPE> The tmsh object type, eg. "apm profile access"
<PROFILE_DEF>  The body of the object, eg.:
    access-policy <PREFIX>_apm
     defaults-from /Common/access
     eps-group <PREFIX>_apm_access_eps
     errormap-group <PREFIX>_apm_access_errormap
     general-ui-group <PREFIX>_apm_access_general_ui

<PROFILE_TYPE> is a catch-all for other APM types, eg:
     apm_sso {
         <PROFILE_TYPE> {apm sso kerberos}
         <PROFILE_DEF>  "account-name <USER>
                         account-password <PASS>
                         realm <REALM>" }

In the example above, <PROFILE_TYPE> and <PROFILE_DEF> are
apm_config meta-tags, while <USER>, <PASS>, and <REALM> must
be substituted before calling apm_config, eg. if these tags are
defined in $pre_proc_map, they may be substituted with:
array set apm_map [string map [subst $pre_proc_map] [array get apm_map]

<RESOURCE_TYPE> The apm resource object type, eg. "webtop"
<RESOURCE_DEF>  The body of the object, eg.:
    "customization-group <ITEM>
     minimize-to-tray false
     webtop-type full"

In the above example, a customization-group is specified. Any
customization-group is assumed to be blank unless further defined by the
<GROUP_DEF> meta-tag, eg. <GROUP_DEF> {type webtop}

<AGENT_TYPE>     default "resource-assign"
<AGENT_DEF>      default "customization-group <ITEM>"
<ITEM_AGENT>     default "agents { <ITEM>_ag { type <AGENT_TYPE> }}"
<ITEM_CAPTION>   default "<ITEM>"
<ITEM_COLOR>     default "1"
<ITEM_TYPE>      default "action"
<ITEM_RULES>     defaults to a set of expressions/next-items where specified
<RULE_CAPTION_0> default "fallback"
<RULE_CAPTION_1> default "Successful"
<RULE_CAPTION_2> default "successful"

apm_config generates the APM agent and customization-group definitions
as required for each policy-item, but specific objects may be defined
by using the <AGENT_DEF> and <GROUP_DEF> meta-tags.
To suppress the formation of an APM agent, specify <ITEM_AGENT> {}.

iapp::upgrade_template upgrade_var upgrade_trans

::server_pools__monitor_recv {
    [set vx(monitor__response) $::server_pools__monitor_recv]
}

::server_pools__monitor_recv {
    [set vx(monitor__response) ##]
}

array set upgrade_trans_arr {
     Yes yes
     server__ntlm { Yes /Common/ntlm }
 }

iapp::downgrade_template pivot_var upgrade_var downgrade_table