kpavel opened a new issue #730: Multiple projects management
   Currently it is impossible to use wskdeploy to  deploy OW assets (action, 
package...etc) of the same signature from different manifests having different 
project names. The problem is that wskdeploy overrides the "managed project" 
annotation. The workaround could be to use different package names, which 
results in assets duplication. Duplication is undesirable, because it 
complicates maintenance. 
   Introducing a feature allowing to manage OW assets by multiple projects 
would help to avoid it.
   - Use different annotation key instead of "manage" for the sake of backward 
compatibility. E.g. `managedList` holding an array of managed project names.
   - On manifest deployment, if a deployed asset already exists in OW, check 
whether the manifest asset is identical to the existing one.
   If not: override the existing asset with the manifest one (similar to the 
current functionality)
   If yes: add the project specified in the manifest to the `managedList`.

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