You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI shows 400 OK error while adding new properties in a custom defined node type. The container logs during the operation are as follows:
54 > POST http://10.15.8.148:8080/winery/nodetypes/example.org.tosca.nodetypes/CustomNode_w1-wip1/propertiesdefinition/
{"winerysPropertiesDefinition":{"namespace":"example.org.tosca.nodetypes","elementName":"CustomNode_w1-wip1","propertyDefinitionKVList":[]},"selectedValue":"Yaml","propertiesDefinition":{"element":null,"type":null,"properties":[{"name":"os","type":"string","description":"","required":true,"defaultValue":"","status":"supported","constraints":[]}],"propertyDefinitionKVList":[]}}
10:10:53.898 [http-nio-8080-exec-6] INFO o.g.jersey.logging.LoggingFeature :149 log - 54 * Server responded with a response on thread http-nio-8080-exec-6
54 < 400
54 < Content-Type: text/plain
Expected YamlPropertiesDefinition element
I tried to create a topology template through REST API (PUT /servicetemplates/com.test/TestAppTopologyTemplate_v1-w1-wip1/topologytemplate) with the json payload of an already created template (through UI) with a couple of nodes and requirement relationships between them.
The nodes are properly created in the new service template TestAppTopologyTemplate_v1-w1-wip1, but the relationships are not visible in the UI.
Hi, I had some issues in using the winery interface.
I tried the opentosca/winery:latest image with below environment settings
(PUT /servicetemplates/com.test/TestAppTopologyTemplate_v1-w1-wip1/topologytemplate)
with the json payload of an already created template (through UI) with a couple of nodes and requirement relationships between them.The nodes are properly created in the new service template TestAppTopologyTemplate_v1-w1-wip1, but the relationships are not visible in the UI.
Kindly guide in resolving the issue. @lharzenetter @wederbn
Thanks.
The text was updated successfully, but these errors were encountered: