You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/02/13 13:10:58 UTC

[GitHub] davidbreitgand commented on issue #730: Multiple projects management

davidbreitgand commented on issue #730: Multiple projects management
URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/730#issuecomment-365262188
 
 
   @pritidesai This is exactly what we had in mind. @lionelvillard The functionality we want to achieve is that there will be only one copy of an annotated asset that when updated retains connections to the projects that it is managed by. It's our understanding that creating a library asset is a possible solution, but with the current implementation, if the user updates the library asset, she will need to call wskdeply for each project that has dependency on that asset and the asset will be overwritten N times in the DB, where N is the number of projects. Having an array of annotations, as @pritidesai suggests seems to be a faster and cleaner way of achieving the result. Thoughts? 

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services