You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/02/09 00:11:52 UTC

[GitHub] pritidesai commented on issue #681: proper handling of 'default' package name

pritidesai commented on issue #681: proper handling of 'default' package name
URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/681#issuecomment-364292402
 
 
   After talking to Matt and scoping this feature of creating OW entities under `namespace/` rather than `namespace/<package>`, its much more feasible (from time, complexity, compatibility, and consistency perspective) to add support for package name `default` in `wskdeploy`. When a package name is set to `default` in manifest/deployment files, `wskdeploy` will generate warnings (1) `Package name 'default' is reserved.` and (2) all OW entities specified in manifest file under `default` package will be created  under your namespace `<namespace>/`.
   
   For example, action `helloNodejs`, trigger `locationUpdate`, and rule `hellorule` in the following example will be created under `<namespace>/` 
   ```
   packages:
      default:
         actions:
           # helloworld action in NodeJS
           helloNodejs:
             function: actions/hello.js
         triggers:
           locationUpdate:
         rules:
           hellorule:
             trigger: locationUpdate
             action: helloNodejs
   ```
   
   Priority: Critical
   
   

----------------------------------------------------------------
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