Knative developer experience, docs, reference Knative CLI implementation
Go to file
Navid Shaikh a264f060c1 Adds missing license to completion.go (#119) 2019-05-20 09:07:27 -07:00
cmd/kn Refactor to allow testing; write first tests. (#10) 2019-01-29 12:40:22 -08:00
docs Adds IBM's IKS to the list of services (update docs) (#131) 2019-05-20 08:57:30 -07:00
hack fix(build.sh): Reintroduced build-flags.sh (#122) 2019-05-17 15:17:09 -07:00
pkg Adds missing license to completion.go (#119) 2019-05-20 09:07:27 -07:00
test Tests running simple workflow in e2e (#112) 2019-05-17 16:42:15 -07:00
vendor Fix auto releases of Knative Client (#124) 2019-05-17 14:40:16 -07:00
.gitignore chore: Update dependencies (#68) 2019-04-30 09:48:33 -07:00
DEVELOPMENT.md Add a Makefile (#83) 2019-05-10 11:58:38 -07:00
LICENSE Initial commit 2018-12-12 16:45:51 -08:00
OWNERS Add OWNERS file, initially with WG leads + evan and matt (#3) 2019-01-10 17:46:31 -08:00
README.md Copy-edit documentation, and make user guide start with installation. (#125) 2019-05-17 16:22:16 -07:00
go.mod Fix auto releases of Knative Client (#124) 2019-05-17 14:40:16 -07:00
go.sum Fix auto releases of Knative Client (#124) 2019-05-17 14:40:16 -07:00

README.md

Knative Client

Knative developer experience best practices, reference Knative CLI implementation, and reference Knative client libraries.

Goals:

  1. Follow closely 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 experimentations and customization

Docs

Start with the user's guide and from there you can can read about common use cases, get detail docs on each command, and even how to extend the kn CLI. Links below for easy access.

Bash auto completion:

Run following to enable bash auto completion

$ source <(kn completion)

Use TAB to list available sub-commands

$ kn <TAB>
completion revision service version

$ kn revision <TAB>
describe get

Developers

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

To build kn, see our Development guide.