bumped version

gerald1248 · Jul 10, 2017 · ca4a056 · ca4a056
1 parent 70cfca0
commit ca4a056
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -41,16 +41,24 @@ Commands:
 
 The main use cases are:
 
-* Command line: this use case assumes you already have a bunch of configuration objects (e.g. the output of `oc export dc --all-namespaces --raw`)
+* Command line: create report based on OpenShift configuration objects
 * Server: you wish to generate reports by posting JSON configuration files to the server at the URL shown
 * GUI: point your browser to the URL shown and fetch current configuration data from the master
 
 ### Command line use
+As part of an automation pipeline, use:
+```
+$ oc export dc,bc,route --raw -o json|openshift-linter
+```
+The `--raw` flag ensures that `namespace` information is available.
+
+If the configuration objects are available as files, enter:
 ```
 $ ./openshift-linter i-contain-multitudes.yaml
 ```
+In this case, both JSON and YAML can be provided.
 
-On the command line, the sample configuration `data/sample-mix.min.json` produces the following markdown output (excerpt):
+The sample configuration `data/sample-mix.min.json`, for example, produces the following markdown output (excerpt):
 
 ```markdown
 image pull policy

diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "openshift-linter",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "description": "basic linter for OpenShift configuration objects",
   "main": "openshift-linter.go",
   "scripts": {