client
client copied to clipboard
knative
Knative developer experience, docs, reference Knative CLI implementation
### Feature request As described in https://github.com/knative/client/pull/964#issuecomment-707184807 the way we are performing the 3way merge for a `kn service apply` is limited and can be improved. ### Use case Instead...
### Feature request Add a new command group `config` for managing `kn` configuration files ### Use case `kn` can be customized by a local configuration file, that e.g. can specify...
## In what area(s)? Classifications: /kind bug ## What version of Knative Client? Version: v20190828-local-f53ebd8 Build Date: 2019-08-28 09:06:01 Git Revision: f53ebd8-dirty Dependencies: - serving: v0.6.0 - eventing: v0.8.0 ##...
## In what area(s)? ## Describe the feature: Debugging and verbose output should be treated in a consistent way over all commands. Currently, we have * `kn plugin list --verbose`...
While the current model of printing a "success" message can be useful for newbies, I actually think it kind of odd since IMO most Linux commands tend to be silent...
Can we add a feature to kn service to check service status after deployment? This feature should be a blocking call to wait for service status to change from Unknown...
When using `--log-http` it would be nice if it didn't write the log to stderr, but appended to a file (either well-defined name, or value specified by the user). Having...
Curently we are using a struct `KnParams` as the _context_ that we pass down into specific commands so that they can access the various services: ```golang type KnParams struct {...
At the moment we have some inconsistencies when it comes to messages. There are also no written rules how messages should look like. Examples: ``` Service 'k8s-event-display' successfully created in...
We have `--force` option while creating a service, the `ConfigurationEditFlags` structure can be restructured as suggested here https://github.com/knative/client/pull/79#discussion_r283004004
