Kálmán Képes

I'm not sure

wouldn't it be a quick and easy way to solve this to send parameter such as CALLEDASSOURCE=true|false and the IA can determine whether it does something or not ?

To add testing the API we need to/should fix https://github.com/OpenTOSCA/container/issues/288 first

[DeploymentTestAgent.csar.zip](https://github.com/OpenTOSCA/container/files/8369765/DeploymentTestAgent.csar.zip) Here is a small example, maybe not deployable, test csar for this PR. Don't forget to rename it from *.csar.zip to *.csar as github doesn't allow .csar endings to...

The whole PR is heavily depending on the following PR: https://github.com/eclipse/winery/pull/665

The only "solution" would be to use a convention, e.g., search first the target stack than the source stack and so on. However, this introduces in some cases more issues...

I can't find anything specific in the standard (1.3 or the upcoming 2.0) which talks about this. Did you find something? They only talk about this a little in 2.0...

If I understand it correctly according to the whole [section](https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969452) we can only use properties of the source and target node(s), not the nodes they are hosted on, e.g., the...

@PhilWun @lharzenetter any insights ?

some test fails and cancels the others but @mar-be and I are looking into and don't find proper issues. The tests run fine locally and after a restart on github...