mrutkows commented on issue #394: Change manifest file to not need specific location of action in rules and sequences URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/394#issuecomment-325361181 @daisy-ycguo Our decision during a Friday call on this was that the 'wskdeploy' tool would automatically pre-pend (if needed) the <package name>/ before any sequences or rules defined withing the same packages (i.e., package:) scope. I believe that Zach indicated in his testing that the action ```process-change``` and the sequence ```process-change-cloudant-sequence``` were both created with the package namespace and could not be found if not specified. That is: ``` package: name: cloudant-trigger # <package_name> ... ... actions: process-change: function: actions/process-change.js sequences: process-change-cloudant-sequence: actions: openwhisk-cloudant/read, <package-name>/process-change rules: log-change-rule: trigger: data-inserted-trigger action: <package-name>/process-change-cloudant-sequence ``` since both the ```process-change``` action and the ```process-change-cloudant-sequence``` were defined within the scope of the package ```cloudant-trigger```. We of course may have to account for namespace collisions if we import another package the has the same sequence or rule name as one locally defined, but we should be able to detect if it has been properly namespaced already. ---------------------------------------------------------------- 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: [email protected]
With regards, Apache Git Services
