container
container copied to clipboard
OpenTOSCA
OpenTOSCA Container - TOSCA Runtime
**Current Behavior:**  The `connectTo` operation between the QHana-Backend and the QHana-PluginRunner gets executed twice. Both times code gets executed at the node of the QHana-Backend. Once, the QHana-Backend is...
#### Short Description Updating the API generation enables us to update the container client properly which we need in another project(s)
#### Short Description Enable general usage of yaml tosca applications #### Proposed Changes - [x] Enable importing YAML csars via given winery importers - [ ] Enable PlanBuilder to work...
#### Short Description #### Proposed Changes * * * **Fixes**: #
#### Short Description Refactor tests into test module and increase test coverage by using the test client to test the API - [x] Move tests into test module - [...
#### Short Description Adds feature to create lifecycle interfaces inside a connectsTo relation, enabling more flexibility. Also is used to align the XML spec to the YAML spec features (just...
#### Short Description Major code cleanup and refactorings for the bus #### Proposed Changes * move model handling code into modelutils * refactor module structure * split processors to increase...
As discussed in #276 .
enables to alter plan generation via the following property in the application.properties: `org.opentosca.plans.sequential=false` Setting it to true would generate the plans to be sequential, enabling easier debugging for example.
If there is an empty DeploymentArtifacts XML Tag inside a Node Type Implementation then planning throws a Null Pointer Exception. This happens e.g. when a Deployment Artifact is added in...
