lionelvillard commented on issue #730: Multiple projects management
   @davidbreitgand in this model, there is only one project:
   P --> A --> B
     |-> C -->  B
   then it's up to wskdeploy to factor out B. When both A and C instantiates B 
with the same parameters, then all is fine. Otherwise wskdeploy can reject or 
decide to deploy B is two different packages (when there is no dynamic 
bindings) or two different namespaces (wskdeploy automatically handles 
   As for `wsk action update b`, I suppose you also mean the user will then use 
`export`. In that case the expected behavior is to update the action in the 
manifest B. However as you said, the OW data model does not support 
dependencies so in order to propagate changes to A and C (like for instance if 
a parameter on b is defined in A) additional annotations must be added to 
encode such dependencies.
   To be clear: I'm not against adding the `managedList` annotation, I'm just 
trying to contrast this approach with the `dependencies` approach. It seems to 
me that in order to let wskdeploy managing dependencies we will need more than 
the `managedList` annotation. 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to