| Table of Contents |
|---|
1.1.1.
...
A Policy Type defines a type of requirement that affects or governs an application or service’s topology at some stage of its lifecycle, but is not explicitly part of the topology itself (i.e., it does not prevent the application or service from being deployed or run if it did not exist).
1.1.1.1.1 Keynames
The Policy Type is a TOSCA Entity and has the common keynames listed in section Error! Reference source not found. TOSCA Entity Schema.
In addition, the Policy Type has the following recognized keynames:
...
Keyname
...
Required
...
Type
...
Description
...
properties
...
no
...
list of
...
An optional list of property definitions for the Policy Type.
targets
...
no
...
string[]
An optional list of valid Node Types or Group Types the Policy Type can be applied to.
Note: This can be viewed by TOSCA Orchestrators as an implied relationship to the target nodes, but one that does not have operational lifecycle considerations. For example, if we were to name this as an explicit Relationship Type we might call this “AppliesTo” (node or group).
...
triggers
...
no
...
list of trigger
...
An optional list of policy triggers for the Policy Type.
1.1.1.1.2 Grammar
Policy Types have the following grammar:
derived_from: <parent_policy_type_name> version: <version_number> metadata: description: <policy_description> properties: targets: [ <list_of_valid_target_types> ] triggers: |
1.1.1.2 SDC Policy Type Metadata
...