Openwhisk: Add ability to list only feeds with CLI

Created on 6 Jun 2016  路  7Comments  路  Source: apache/openwhisk

A feed is an action with a feed=true annotation.
We can enhance the wsk action list to filter for feeds like wsk action list --feed

Another alternative is to treat feed as first class objects, and have a feed command like wsk feed list

Making a the new command:

$ wsk action -h
usage: wsk feed [-h] {create,update,get,delete,list} ...

optional arguments:
  -h, --help            show this help message and exit

available commands:
  {create,update,invoke,get,delete,list}
    create              create new action
    update              update an existing action
    get                 get action
    delete              delete action
    list                list all actions

cc @mbehrendt

cli enhancement

Most helpful comment

our emoji voting 馃槃 in https://github.com/openwhisk/openwhisk/issues/575#issuecomment-224343620 seems to indicate that making them look like first class will be handle client side (i.e. CLI, UI, etc..)

All 7 comments

to list feeds, a developer using whisk should _never_ have to know that feeds are implemented as actions (actions are just impl choices). an event provider creating feeds has to know that, but not a regular user.

i'd suggest to either expose feeds as a first class entity or allow listing them with a parameter to wsk package list, eg wsk package list -feeds

Hum wsk package list feels wrong, this command it's about listing only packages, wsk package get $name or wsk package get $name --summary it's about list the package content.

This will get you the summary of the specified package like:

$ wsk package get myGit --summary
package /[email protected]_dev/myGit
 feed   /[email protected]_dev/myGit/webhook: Creates a webhook on github to be notified on selected changes

What about wsk list listing feeds?

Today it wsk list prints a summary for packages actions triggers and rules but it doesn't list feeds

for example the feed /[email protected]_dev/myGit/webhook
Can be listed very easily with wsk list like this:

$ wsk list

entities in namespace: [email protected]_dev
packages
/[email protected]_dev/myGit private binding
actions
/[email protected]_dev/echo private
triggers
/[email protected]_dev/myGitTrigger private
rules
/[email protected]_dev/ifGitThenEcho private
feeds
/[email protected]_dev/myGit/webhook private

If wsk list lists feeds, I as a user expect to be able to do something like wsk feed get as I can do that with all the other entities. That'ld strenghten @mbehrendt 's point of having feeds as first-class entities, at least on CLI level.

I'm in agreement that it should be first class citizen and on top of that also be listed in wsk list

The bigger question is should the REST API supports them as first class citizens not just the CLI?

no.

our emoji voting 馃槃 in https://github.com/openwhisk/openwhisk/issues/575#issuecomment-224343620 seems to indicate that making them look like first class will be handle client side (i.e. CLI, UI, etc..)

Was this page helpful?
0 / 5 - 0 ratings