Component Types template
Component types are defined using a YAML manifest with the following structure:
and properties for the general section:
Field | Type | Value restrictions | Is required | Default value | Description |
---|---|---|---|---|---|
| string | should match the following regexp:
that is only letters, number and underscores, no initial number of underscore Notice: this should not match the name of another component | TRUE |
| The name of the component. |
| string |
| TRUE |
| A description to characterize the component. |
| string | notice: this should match the name of an existing component-type | TRUE |
| The name of the component-type that defines the type of the component. |
| object |
| FALSE |
| General custom properties of the component. These properties can be defined freely and usually have the purpose to expose information useful for configuring the component. |
The parameter section describes the relationship between the component type and already defined parameters with the following properties:
Field | Type | Value restrictions | Is required | Default value | Description |
---|---|---|---|---|---|
| string | It should match the name of an existing parameter. | Yes | - | The name of the parameter that should be related to the component-type |
| string | {real, integer, categorical} | Yes | - | The type of domain to be set for the parameter in relationship with the component-type |
| array of numbers | The numbers should be either all integers or real numbers(do not omit the " . ") depending on The size of the array must be 2. | No | - | The bounds to be used to define the domain of the parameter. These bounds are inclusive |
| array of strings |
| No | - | The possible categories that the parameter could possess |
| string, integer, real | The value must be included in the domain, for real and integer types and must be a value included in the categories | Yes | - | The default value of the parameter |
| integer | [0-255] | No | 5 | The number of decimal digits rendered for this parameter |
| object | The name and the parameters of a supported workflow operators | TRUE | - | Specify what operators can be used to apply the parameter |
The metric section describes the relationship between the component type and already defined metrics with the following properties:
Field | Type | Value restrictions | Is required | Default value | Description |
---|---|---|---|---|---|
name | string | It should match the name of an existing metric | TRUE | The name of the metric that should be related to the component type |
Notice that component type definitions are shared across all the workspaces on the same Akamas installation, and require an account with administrative privileges to manage them.
Examples
Example of a component for the Cassandra component type:
Example of a component for the Linux operating component type:
Last updated