Knative developer experience, docs, reference Knative CLI implementation
Go to file
David Simansky b14dc2dc7f
feat(wait): add sync revision delete operation (#688)
2020-02-29 06:09:51 -08:00
.github chore: Add some clarification to the pull request template for where to put CHANGELOG entries (#494) 2019-11-12 02:14:23 -08:00
cmd/kn remove printing err when running root command (#615) 2020-01-21 09:58:05 -08:00
config Update serving dependency to 0.8; change all import paths (#368) 2019-08-15 18:09:08 -07:00
conventions feature(serving): Update API to serving.knative.dev/v1 (#640) 2020-02-07 02:03:14 -08:00
docs feat(wait): add sync revision delete operation (#688) 2020-02-29 06:09:51 -08:00
hack chore(build): Spacing fix for newer iTerm (>=3.3.7) (#509) 2019-11-19 05:12:07 -08:00
pkg feat(wait): add sync revision delete operation (#688) 2020-02-29 06:09:51 -08:00
test fix for the failure of trigger e2e test (#690) 2020-02-28 02:36:51 -08:00
vendor chore(e2e): Refactor to better track errors (#667) 2020-02-16 23:52:10 -08:00
.gitignore Explicit name for serving client (#537) 2019-12-08 23:42:44 -08:00
CHANGELOG.adoc Add --user flag for service create and update (#679) 2020-02-28 03:55:51 -08:00
DEVELOPMENT.md Add readme for tests (#554) (#555) 2019-12-16 23:18:02 -08:00
LICENSE Initial commit 2018-12-12 16:45:51 -08:00
OWNERS Adds Navid (@navidshaikh) to approvers list (#321) 2019-07-31 13:59:43 -07:00
README.md Adds zsh completion (#476) 2019-11-05 02:42:25 -08:00
go.mod chore(e2e): Refactor to better track errors (#667) 2020-02-16 23:52:10 -08:00
go.sum chore(e2e): Refactor to better track errors (#667) 2020-02-16 23:52:10 -08:00

README.md

Knative Client

This section outlines best practices for the Knative developer experience. It is a reference for Knative CLI implementation, and a reference for Knative client libraries.

The goals of the Knative Client are to:

  1. Follow the Knative serving and eventing APIs
  2. Be scriptable to allow users to create different Knative workflows
  3. Expose useful Golang packages to allow integration into other programs or CLIs or plugins
  4. Use consistent verbs, nouns, and flags for various commands
  5. Be easily extended via a plugin mechanism (similar to kubectl) to allow for experimentation and customization

Docs

Start with the user's guide to learn more. You can read about common use cases, get detailed documentation on each command, and learn how to extend the kn CLI. For more information, access the following links:

Shell auto completion:

Run the following command to enable shell auto-completion:

For Zsh:

$ source <(kn completion zsh)

For Bash:

$ source <(kn completion bash)

Use TAB to list available sub-commands or flags.

Developers

If you would like to contribute, please see CONTRIBUTING for more information.

To build kn, see our Development guide.