daisy-ycguo commented on issue #437: Question about dependency name and the origin package name URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/437#issuecomment-327362805 I verified and I think package binding can help this use case. I made following test. 1. create package `IntegrationTestHelloWorld` by `wskdeploy -p tests/src/integration/helloworld` 2. create a binding package newpkg by `wsk package bind IntegrationTestHelloWorld newpkg`, and then get the newpkg by `wsk package get --summary newpkg`, I see all the actions are listed: ``` package /[email protected]_dev/newpkg action /[email protected]_dev/newpkg/hello-world-series action /[email protected]_dev/newpkg/helloSwift action /[email protected]_dev/newpkg/helloPython action /[email protected]_dev/newpkg/helloJava action /[email protected]_dev/newpkg/helloNodejs ``` 3. create another binding package newnewpkg by `wsk package bind IntegrationTestHelloWorld newnewpkg` and then get the newnewpkg by `wsk package get --summary newnewpkg`, all the actions are listed too. 4. invoke an action of newpkg by `wsk action invoke -r newpkg/helloJava`, the correct result is returned. ``` { "greeting": "Hello Bob!" } ``` So I think, to this use case, we can create the original package at first, and then create binding with the new dependency name if the dependency name is different from the original package name. What's more, users can use inputs here as a binding to the original package. ---------------------------------------------------------------- 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
