Unstructured Resources

Some configuration objects are not expressed as key/value pairs, but rather inline as raw text. Examples of these include TrafficScript rules, SSL certificates, and custom monitor scripts.

When using the REST API, you upload such configuration objects using a PUT request with a content-type of "application/octet-stream".

To present the raw data in a configuration document, use a "content" field. Declare the data either inline or as an indented block using a YAML literal scalar (designated by the '|' indicator). The following example expresses a TrafficScript rule:

rules:
- name: basic-response
content: |
http.sendResponse("200 OK", "text/plain", "Hello World\n", "X-Served-By: Ivanti vTM");

For binary files, content can be base64 encoded with an "encoding: base64" field added to the object definition. For details of the supported base64 type requirements, see RFC2045 (https://www.ietf.org/rfc/rfc2045.txt).

Alternatively, you can import values from an external file using the object reference syntax described in Object References.