Application Delivery Management

Create and use custom StyleBooks

December 31, 2023

Contributed by:

You can write your own StyleBook for your deployment, import it to Citrix Application Delivery Management (ADM), and create configuration objects. You can also use API to create configurations from your StyleBooks.

This document includes the following information:

Before you begin

Before you begin creating StyleBooks, make sure you have knowledge of the following:

NITRO API. For more information, see Nitro API documentation
YAML

StyleBook files use the YAML format. For information about the YAML format, see YAML Syntax.

The following is a list of YAML guidelines you must be aware of while creating StyleBooks:

YAML is case sensitive.
YAML requires proper indentation
Use <spacebar> key to create proper indentation. Do not use <tab> key. Using <tab> key creates compilation error while importing your StyleBook to MA Service.
Do not use strings within quotation marks. Include the string within quotation marks only if a string contains punctuation marks (dashes, colons, and so on.) If you want to interpret a number as a string, either include the number within quotation marks or use the str() built-in function of StyleBooks.
Literals like YES/Yes/yes/Y/y/NO/no/No/n/N, ON/On/on/OFF/Off/off, and TRUE/true/truthy/FALSE/False/false/falsely are considered Booleans, and are equivalent to true and false respectively. To interpret them as strings, include them within quotation marks. For example:
- “YES”
- “No”
- “True”
- “False” and so on.

Note

Before importing your StyleBook file into Citrix ADM, it is recommended that you validate if your file is compliant with the YAML format. Citrix recommends that you use the built-in YAML validator in StyleBooks to validate and import the YAML content.

While configuring StyleBooks, you can only use Nitro Configuration resources that support the Create and Delete operations (POST and DELETE HTTP methods). For more information, see Nitro APIs documentation.

Anatomy of a StyleBook

Writing StyleBooks requires that you understand the grammar, syntax, and structure of StyleBooks. A typical StyleBook has the following sections:

Header: This section lets you define the identity of a StyleBook and describe what it does. This is a mandatory section.
Import StyleBooks: This section lets you declare which other StyleBook you want to refer to from your current StyleBook. Importing Citrix ADC NITRO configuration StyleBooks or other StyleBooks is required to write a StyleBook. This is a mandatory section.
Parameters: This section lets you define the parameters you require in your StyleBook to create a configuration. It describes the input that your StyleBook takes. This is an optional section.
Components: This section lets you define the entities (configuration objects) that are created by the StyleBook for a specific configuration. This section is considered as the core of a StyleBook. Components generally use the input provided in the parameters section to adapt the configuration generated by the StyleBook. This is an optional section.

A StyleBook may have a parameters section, or a components section, or both. A StyleBook with only the parameters section is useful to define a list of parameters that can be used by other StyleBooks. This promotes reusability of parameter groups across a set of StyleBooks. A StyleBook with only a components section may be used when you want to specify the values for attributes in the StyleBook instead of defining parameters to take user input.
Outputs: While the parameters section defines the inputs of the StyleBook, this optional section defines its outputs. In this optional outputs section, you can specify the components that you want to expose to users creating a configuration from this StyleBook and to other StyleBooks that import this StyleBook. Users and importing StyleBooks can then reference the properties of the exposed components.
Operations: A StyleBook may contain an optional section to enable Analytics in Citrix ADM on any virtual server that is part of the StyleBook.

The following figure shows a simple outline of a StyleBook.

localized image

The following examples help you learn about the grammar and structure of a StyleBook and how to write StyleBooks with increasing levels of complexity.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Create and use custom StyleBooks

December 31, 2023

Contributed by:

December 31, 2023

Contributed by:

Create and use custom StyleBooks

Before you begin

Anatomy of a StyleBook

In this article