-
## Description
When `get_input` function is used inside a nested type, e.g. `map `property, then it is not evaluated and passed to playbook as it is.
## Steps
When deploying the following service t…
-
As several partners need to parse TOSCA files to extract information, one idea would be to make the Opera parser available as a library.
From our (CTT) point of view it would be probably enough to ha…
-
## Description
The orchestrator allows passing inputs while deploying TOSCA templates/CSARS. These inputs are passed as a YAML file containing key: value pairs for TOSCA inputs. The usual process fea…
-
The [ security tool bandit ](https://github.com/PyCQA/bandit) founds 4 medium issues related to yaml_load in follwing files :
- bin/cloudnet/tosca/configuration.py:32
- bin/cloudnet/tosca/importers…
-
## Description
This issue is meant for the discussion about opera init command which might be uneeded.
The latest version [`0.6.1`](https://github.com/xlab-si/xopera-opera/releases/tag/0.6.1) of `…
-
## Description
In this issue we describe a proposal for enabling opera to compare the existing Deployed Instance model (*DI1*) with a changed/reconfigured Deployable Instance model (*DI2*) defined wi…
dradX updated
3 years ago
-
The TOSCA standard treats all number values in the yaml files as strings, e.g.:
all
`count: 5`
should be
`count: "5"`
see example in the figure:
, files are o…
-
Hi,
I am working with TOSCA modelling of data pipelines. I have prepared a service template using Winery. The service template consists of creating an instance in private cloud (OpenStack Environmen…
-
In the case of the CSAR-tree, the orchestrator ignores the referenced file defined in the main TOSCA yaml and returns a
[Path] Path does not exist.
type of error. The referenced file is in the …