Data Types

Supported data types

Following data types are supported:

• none: No value: none
• any: Any value: any
• boolean: Boolean value: true or false
• unsigned: Unsigned number. Examples: 10, 6000
• enum: Unsigned numeric enum. Examples: START, radius, 1, 2
• signed: Signed number. Examples: -10, -6000, 10, 6000
• float: Floating point number. Examples: 3.5, 20.9
• timestamp: Timestamp. Examples: now, RFC 2822 format, RFC 3339 format
• duration: Duration with optional unit suffixes. Examples: 5s, 30m, 2h, 1d. See Duration Units
• string: Text string. Examples: "some text", word
• bytes: Bytes. Examples: 0xaa00ffee
• ip: IPv4 or IPv6 address. Examples: 10.10.10.10, 2001:db8:3333:4444:5555:6666:7777:8888
• ip-prefix: IPv4 or IPv6 address prefix. Examples: 10.10.10.0/24, 2001:db8::/32
• regex: Regular expression. Example: /^example.(com|org)$/

If a namespace attribute has no value, none is returned.

String Syntax

Strings are enclosed in double quotes "like this" or in triple quotes """like this""". Triple quoted strings can span multiple lines and they can contain unescaped double quotes. Strings can contain variable expansions like "Hello %{vars.username}". These are called Format Strings.

In execution pipelines the variable can refer to the execution context, for example %{user.username} but elsewhere it can only access the process environment variables like %{env.PATH}. The variable expansions can also contain filters like %{env.USER | uppercase}. See Filters for more information. Non-execution context