mirror of https://github.com/knative/client.git
Fixes #364 - Ensure kn cross platform build works in pre-submit tests - Run ./hack/build.sh -x after running existing pre-submit tests - defines a function post_build_tests to invoke cross platform builds - post_build_tests will be run by test-infra after build tests are compelete |
||
---|---|---|
.github | ||
cmd/kn | ||
config | ||
conventions | ||
docs | ||
hack | ||
pkg | ||
test | ||
vendor | ||
.gitignore | ||
CHANGELOG.adoc | ||
DEVELOPMENT.md | ||
LICENSE | ||
OWNERS | ||
README.md | ||
go.mod | ||
go.sum |
README.md
Knative Client
This section outlines best practices for the Knative developer experience, is a reference for Knative CLI implementation, and a reference for Knative client libraries.
The goals of the Knative Client are to:
- Follow the Knative serving and eventing APIs
- Be scriptable to allow users to create different Knative workflows
- Expose useful Golang packages to allow integration into other programs or CLIs or plugins
- Use consistent verbs, nouns, and flags for various commands
- 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:
- User's guide
- Basic workflows (use cases)
- Generated documentation
Bash auto completion:
Run the following command 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 would like to contribute, please see CONTRIBUTING for more information.
To build kn
, see our Development guide.