[GitHub] zachschultz opened a new issue #317: Action deployed with .php extension defaulted to a Node runtime

[git]

zachschultz opened a new issue #317: Action deployed with .php extension 
defaulted to a Node runtime
URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/317
 
 
   My manifest file looks like:
   
   ```
   # Wskdeploy manifest for openwhisk-cloudant-trigger
   # GitHub repo is located at 
https://github.com/IBM/openwhisk-message-hub-trigger
   
   # Deployment using this manifest file creates the following OpenWhisk 
components:
   #   Package:  openwhisk-messagehub
   #   Package:  messagehub-trigger
   #   Action:   messagehub-trigger/process-message.js
   #   Sequence: messagehub-trigger/process-message-messagehub-sequence
   #   Trigger:  message-received-trigger
   #   Rule:     log-message-rule
   
   # This manifest file reads the following env. variables:
   #   KAFKA_BROKERS
   #   MESSAGEHUB_USER
   #   MESSAGEHUB_PASS
   #   KAFKA_TOPIC
   
   package:
     name: messagehub-trigger
     version: 1.0
     license: Apache-2.0
     namespace: _
     dependencies:
       openwhisk-messagehub:
         location: /whisk.system/messaging
         inputs:
           kafka_brokers_sasl: $KAFKA_BROKERS
           user: $MESSAGEHUB_USER
           password: $MESSAGEHUB_PASS
           kafka_admin_url: $KAFKA_ADMIN_URL
     actions:
       process-message:
         location: runtimes/php/actions/process-message.php
     triggers:
       message-received-trigger:
         source: openwhisk-messagehub/messageHubFeed
         inputs:
           isJSONData: true
           topic: $KAFKA_TOPIC
     rules:
         log-message-rule:
           trigger: message-received-trigger
           action: messagehub-trigger/process-message
   ```
   
   After running `wskdeploy` I noticed that my deployed action happened to be 
the Node runtime, and naturally didn't run correctly.
 
----------------------------------------------------------------
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