For a Data processing App from MessageHub changes there is a wskdeploy manifest available for a user to easily instantiate the PRODUCT

[krook]

[krook]

@mrutkows Please assign. Assuming @daisy-ycguo or @lzbj.

[daisy-ycguo]

depends on openwhisk/openwhisk-wskdeploy issue #101

[krook]

Need to also consider "Deploy to Bluemix" type of button for driving wskdeploy and doing continuous testing to ensure the app doesn't break with upstream changes.

[lzbj]

So we need to put the manifest.yml under this repo to trigger the wskdeploy?

[daisy-ycguo]

I think we can do below things:

• Create a wskdeployinstall.sh to install wskdeploy in the user's local environment, including the configuration file to set the env variables, e.g. apihost and etc.
• Prepare manifest.yml and deployment.yml at the repo root, which can be used by wskdeploy
• Change the document to guide users how to deploy with wskdeploy tool.

So when we demonstrate this use case, the command lines should be:

1. git clone .... ( clone this repo into local disk )
2. ./wskdeployinstall.sh ( install wskdeploy and config env variables )
3. wskdeploy ( run wskdeploy to deploy to bluemix server)

@krook Let me know how do you want to show the demo. I don't quite understand consider "Deploy to Bluemix" type of button for driving wskdeploy and doing continuous testing to ensure the app doesn't break with upstream changes. It looks like you are going to use the WSK UI in bluemix.

[mrutkows]

Carlos, indicated we should not "re-invent the wheel" and use what is already available for the CLI on the backend where it already uses gradle commands to build a Docker container for building the binarie(s). Then a webapp (web page) can be constructed to invoke wskdeploy as an whisk action.

Here are his comments from Slack earlier:
yes you ca prototype the app today using whisk and what daisy is correct

./wskdeployinstall.sh ( install wskdeploy and config env variables )
wskdeploy ( run wskdeploy to deploy to bluemix server)

[1:18]
basically running this on behave of the user but from a browser

[1:20]
and also to make it fast the wskdeploy binary should already be available some where to do curl https://github.com/openwhisk/openwhisk-wskdeploy/archive/linux/wskdeploy

[1:23]
you can implement the webpage using a web action, the html page will ask user to enter bluemix username and password to login/deploy, then present select namespace to deploy app to, text input will have ow key for the namespace, text input will be populated with getting started git url via query parameter from button/link. when clicking submit, invoke another action that will do the 3 steps, that daisy said clone, setup, wskdeploy, return a 301 to openwhisk ui