Add munger to verify kubectl -f targets, fix docs
This commit is contained in:
@@ -36,7 +36,7 @@ const (
|
||||
|
||||
JSON and YAML formats are accepted.`
|
||||
create_example = `// Create a pod using the data in pod.json.
|
||||
$ kubectl create -f pod.json
|
||||
$ kubectl create -f ./pod.json
|
||||
|
||||
// Create a pod based on the JSON passed into stdin.
|
||||
$ cat pod.json | kubectl create -f -`
|
||||
|
@@ -43,7 +43,7 @@ Note that the delete command does NOT do resource version checks, so if someone
|
||||
submits an update to a resource right when you submit a delete, their update
|
||||
will be lost along with the rest of the resource.`
|
||||
delete_example = `// Delete a pod using the type and name specified in pod.json.
|
||||
$ kubectl delete -f pod.json
|
||||
$ kubectl delete -f ./pod.json
|
||||
|
||||
// Delete a pod based on the type and name in the JSON passed into stdin.
|
||||
$ cat pod.json | kubectl delete -f -
|
||||
|
@@ -35,13 +35,13 @@ const (
|
||||
|
||||
JSON and YAML formats are accepted.`
|
||||
replace_example = `// Replace a pod using the data in pod.json.
|
||||
$ kubectl replace -f pod.json
|
||||
$ kubectl replace -f ./pod.json
|
||||
|
||||
// Replace a pod based on the JSON passed into stdin.
|
||||
$ cat pod.json | kubectl replace -f -
|
||||
|
||||
// Force replace, delete and then re-create the resource
|
||||
kubectl replace --force -f pod.json`
|
||||
kubectl replace --force -f ./pod.json`
|
||||
)
|
||||
|
||||
func NewCmdReplace(f *cmdutil.Factory, out io.Writer) *cobra.Command {
|
||||
|
Reference in New Issue
Block a user