-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of NetScaler application configuration using StyleBooks
-
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!
Create a StyleBook to perform non-CRUD operations
StyleBooks manage NetScaler configurations by computing the necessary configuration objects on the NetScaler instances. These objects are added, updated or removed from the instance each time you create or update a ConfigPack. That is when you specify the “desired state.”
However, some NetScaler configuration objects support a few operations other than create, update or delete (CRUD operations). For example, a load balancer object (lbvserver) or a NetScaler feature object (nsfeature) can support the “enable” or “disable” operation. Similarly, NetScaler certkeys support the “link” and “unlink” operation to link or unlink a certificate to another certificate. These operations on NetScaler objects are called as non-CRUD operations. This section describes how to perform non-CRUD operations on configuration objects that support them using StyleBooks.
Note
The binding between configuration objects (for example, bind a certkey to a lbvserver) is not considered a non-CRUD operation. This is because Nitro bindings are represented as configuration objects in their own right. These objects are created and deleted like any other NetScaler configuration object.
Supporting the non-CRUD operations
A new construct called “meta-properties” is added in the component at the same level as the “properties” construct. The only attribute supported in this construct currently is called “action” This attribute can take values like “enable” or “disable” that are supported by that configuration object.
components:
-
name: my-lbvserver-comp
type: ns::lbvserver
meta-properties
action: enable
properties:
name: $parameters.name
servicetype: HTTP
ipv46: $parameters.ip
port: 80
lbmethod: $parameters.lb-alg
<!--NeedCopy-->
In the above example, the “my-lbvserver-comp” component is of type “ns::lbvserver.” The “ns” is the prefix that refers to the namespace netscaler.nitro.config and version 10.5 that you had specified in the import-stylebooks section. The “lbvserver” is a NITRO resource in this namespace. As an implicit action, the lbvserver is first created by the StyleBook; then the “enable” operation is performed on it.
The action specified in the meta-properties is performed on the configuration object only during the creation of the ConfigPack. Updates to the ConfigPack do not perform non-CRUD actions.
Note
The value of the action attribute cannot be a StyleBook expression that is evaluated dynamically.
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.