[GitHub] pritidesai opened a new issue #399: Error out when env. variables from manifest/deployment are not defined

[gi...@git.apache.org]

pritidesai opened a new issue #399: Error out when env. variables from manifest/deployment are not defined
URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/399
 
 
   Incorporating env. variables into a manifest or deployment file is supported practice with wskdeploy. Its very common to run wskdeploy without setting those env. variables. In such situations, wskdeploy fails with this cryptic message:
   
   ```
   ./wskdeploy -m ~/IBM/OpenWhisk/source/zachschultz/owbp-cloudant-trigger/runtimes/node/manifest.yaml 
   2017/08/28 12:35:41 Deploying package cloudant-trigger ... 
   2017/08/28 12:35:41 Done!
   Deploying dependency openwhisk-cloudant ... 
   2017/08/28 12:35:41 Deploying package bindingopenwhisk-cloudant ... 
   2017/08/28 12:35:41 Done!
   2017/08/28 12:35:41 Deploying action cloudant-trigger/process-change ... 
   2017/08/28 12:35:42 Done!
   2017/08/28 12:35:42 Deploying action cloudant-trigger/process-change-cloudant-sequence ... 
   2017/08/28 12:35:42 Done!
   2017/08/28 12:35:42 Deploying trigger feed data-inserted-trigger ... 
   2017/08/28 12:35:43 Got error creating trigger feed with error message: The following application error was received: {} and error code: 246.
   Done!
   Deploying rule log-change-rule ... Done!
   2017/08/28 12:35:44 
   Deployment completed successfully.
   ```
   
   (I am using Zach's manifest here)
   
   We should instead report that the essential env. variables are not defined and error out instead of reporting this kind of error.
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services