should wsk action invoke be blocking by default?
Open
question
- Dominant language
- Go
- Stars
- 109
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
today `wsk action invoke` is asynchronous and one must do `-b` or `-r` to get a blocking activation --- it seems that almost always when developing and testing the common case is for a blocking invoke.
should we flip the default and add `-a` for async?
Contributor guide
Assessment
This issue has not been assessed yet.