-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of NetScaler application configuration using StyleBooks
-
-
Header
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Header
The first six lines of a StyleBook comprise the header section. This section lets you define the identity of a StyleBook and describe what it does. This is a mandatory section.
The following table describes the attributes of the header section:
Attribute | Description |
---|---|
name | A name to identify the StyleBook. This attribute is mandatory. |
display-name | A descriptive name for the StyleBook. This name appears on the NetScaler ADM GUI. This is an optional attribute. |
description | A description text defines what this StyleBook do. This description appears on the ADM GUI. This is an optional attribute. Note: This is an HTML fragment and you can use HTML tags to customize headings or insert images using the <img> tag with URLs or embedded images. |
author | The author person or organization who creates the StyleBook. This is an optional attribute. |
namespace | A namespace forms part of a unique identifier for a StyleBook to avoid name collisions. A namespace can be any string, but a good practice is to use it for naming the company, department, or unit that created or owns a set of StyleBooks. For example, you can use the following format: <company>.<department>.<unit>.stylebooks . This is a mandatory attribute. |
version | The version number of the StyleBook. You can change the version number when you update a StyleBook. StyleBooks of different versions can co-exist together. This is a mandatory attribute. |
schema-version | The version of the StyleBooks schema. It takes the value “1.0” in the current release of NetScaler ADM. This is a mandatory attribute. |
private | If this attribute is set to true, the StyleBook is not displayed on the NetScaler ADM GUI. This is a useful setting for StyleBooks that are building blocks for other StyleBooks and are not intended to be used by users directly. This is an optional attribute. Its default value is false. |
Example:
name: lb
description: "This stylebook defines a sample load balancing configuration."
display-name: "Load Balancing StyleBook (HTTP)"
author: Mike Smith (ACME Infra team)
namespace: com.example.stylebooks
schema-version: "1.0"
version: "0.1"
<!--NeedCopy-->
The combination of name, namespace, and version uniquely identifies a StyleBook in the system. You cannot have two StyleBooks with the same combination of name, namespace, and version in NetScaler ADM. However, you can have two StyleBooks with the same name and version but different namespaces, or with the same namespace and version but different names.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.