[GitHub] mrutkows commented on issue #730: Multiple projects management
mrutkows commented on issue #730: Multiple projects management URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/730#issuecomment-374961737 @davidbreitgand Using your example of, A -> B and project C -> B, my initial reaction is that I do not support making any changes to project B's annotations. As described, it seems that project B has value (as providing a library/shared asset) and should be marked public/shared by its owner (different owner than project A and project C). From a security point of view (and existing dependency paradigms) we should never alter another person's assets even if we are only affecting their annotations. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mrutkows commented on issue #730: Multiple projects management
mrutkows commented on issue #730: Multiple projects management URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/730#issuecomment-365272165 @pritidesai if we move to a nested map, as we discussed yesterday within the annotations, I would prefer that we attempt to simulate a key-only "tag" which is URI based. Where the URI includes information regarding the project and project hash. It is my hope still that we will eventually move to a flatter single-value URI for faster lookup/comparison. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mrutkows commented on issue #730: Multiple projects management
mrutkows commented on issue #730: Multiple projects management URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/730#issuecomment-365272165 @pritidesai if we move to a nested map, as we discussed yesterday within the annotations, I would prefer that we attempt to simulate a key-only "tag" which is URI based. Where the URI includes information regarding the project and project hash. It is my hope still that we will need to move to a flatter single-value URI for faster lookup/comparison. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mrutkows commented on issue #730: Multiple projects management
mrutkows commented on issue #730: Multiple projects management URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/730#issuecomment-365272165 @pritidesai if we move to a nested map, as we discussed yesterday within the annotations, I would prefer that we attempt to simulate a key-only "tag" which is URI based. Where the URI includes information regarding the project and project hash. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] mrutkows commented on issue #730: Multiple projects management
mrutkows commented on issue #730: Multiple projects management URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/730#issuecomment-364995703 @kpavel as discussed elsewhere... the plan would be to use URI "tags" where there is no key (each project name would be clearly part of the URI) along with domain/path to indicate that this is a "managed project" tag. 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: us...@infra.apache.org With regards, Apache Git Services
