Commit 46a39f02 authored by Laurent Ganne's avatar Laurent Ganne
Browse files

New plugins

parent d1f3ca81
No preview for this file type
No preview for this file type
......@@ -48,7 +48,7 @@ topology_template:
token: { get_input: token }
JobSpecification:
Name: WRFJob
...
...
# Outputs: values of attributes exposed by components described above
outputs:
ddi_post_process_results:
......@@ -203,3 +203,54 @@ thanks to these lines in the import section:
imports:
- heappe-types:1.0.3
```
## Section topology_template
This section describes input parameters, components and relationships, outputs,
and workflows of the application
### subsection inputs
In this subsection you declare input parameters, specifying which one are required
and which one are not required with a default value that the user can override if needed.
Here is the description on an input parameter `token` marked as required,
so the user will have to provide a value to this input parameter before being able to deploy the application:
```bash
topology_template:
# Input parameters provided by the user and referenced in node templates below
inputs:
token:
type: string
required: true
description: "Access token"
```
These input parameters can be referenced in the next section node_templates in
propertied of node templates, using the TOSCA function `get_input` like below:
```yaml
WRF_DAY_1:
type: org.heappe.nodes.Job
properties:
token: { get_input: token }
```
### subsection node_templates
This subsection describes components and relationships between this component
# Description of components and relationships between these components
node_templates:
# Here a HEAppE job referencing in its properties the token input parameter
WRF_DAY_1:
type: org.heappe.nodes.Job
metadata:
task: computation
properties:
token: { get_input: token }
JobSpecification:
Name: WRFJob
...
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment