doc/{ansible,helm}/dev: 'up local' -> 'run --local' (#2455)

Author: Eric Stroczynski

doc/ansible/dev/developer_guide.md

@@ -187,13 +187,13 @@ annotations:
 
 Once a developer is comfortable working with the above workflow, it will be
 beneficial to test the logic inside of an operator. To accomplish this, we can
-use `operator-sdk up local` from the top-level directory of our project. The
-`up local` command reads from `./watches.yaml` and uses `~/.kube/config` to
+use `operator-sdk run --local` from the top-level directory of our project. The
+`run --local` command reads from `./watches.yaml` and uses `~/.kube/config` to
 communicate with a Kubernetes cluster just as the `k8s` modules do. This
 section assumes the developer has read the [Ansible Operator user
 guide][ansible_operator_user_guide] and has the proper dependencies installed.
 
-Since `up local` reads from `./watches.yaml`, there are a couple options
+Since `run --local` reads from `./watches.yaml`, there are a couple options
 available to the developer. If `role` is left alone (by default
 `/opt/ansible/roles/<name>`) the developer must copy the role over to
 `/opt/ansible/roles` from the operator directly. This is cumbersome because
@@ -218,9 +218,9 @@ $ kubectl create -f deploy/role.yaml
 $ kubectl create -f deploy/role_binding.yaml
 ```
 
-Run the `up local` command:
+Run the `run --local` command:
 ```bash
-$ operator-sdk up local
+$ operator-sdk run --local
 INFO[0000] Go Version: go1.10.3
 INFO[0000] Go OS/Arch: linux/amd64
 INFO[0000] operator-sdk Version: 0.0.6+git
@@ -441,14 +441,14 @@ Please look over the following sections for help debugging an Ansible Operator:
 * [Additional Ansible debug](../user-guide.md#additional-ansible-debug)
 * [Testing Ansible Operators with Molecule](testing_guide.md#testing-ansible-operators-with-molecule)
 
-### Using k8s_status Ansible module with `up local`
+### Using k8s_status Ansible module with `run --local`
 This section covers the required steps to using the `k8s_status` Ansible module
-with `operator-sdk up local`. If you are unfamiliar with managing status from
+with `operator-sdk run --local`. If you are unfamiliar with managing status from
 the Ansible Operator, see the [proposal for user-driven status
 management][manage_status_proposal].
 
 If your operator takes advantage of the `k8s_status` Ansible module and you are
-interested in testing the operator with `operator-sdk up local`, then
+interested in testing the operator with `operator-sdk run --local`, then
 you will need to install the collection locally.
 
 ```sh

doc/helm/dev/developer_guide.md

@@ -320,8 +320,8 @@ being released by the operator.
 
 Once a developer is comfortable working with the above workflow, it will be
 beneficial to test the logic inside of an operator. To accomplish this, we can
-use `operator-sdk up local` from the top-level directory of our project. The
-`up local` command reads from `./watches.yaml` and uses `~/.kube/config` to
+use `operator-sdk run --local` from the top-level directory of our project. The
+`run --local` command reads from `./watches.yaml` and uses `~/.kube/config` to
 communicate with a Kubernetes cluster just as the `helm` CLI commands did
 when we were testing our Helm chart locally. This section assumes the developer
 has read the [Helm Operator user guide][helm_operator_user_guide] and has the
@@ -334,12 +334,12 @@ inside of the `deploy` folder:
 kubectl create -f deploy/crds/foo.example.com_foos_crd.yaml
 ```
 
-**NOTE:** When running the Helm operator locally, the `up local` command will default to using the kubeconfig file specified by `$KUBECONFIG` with a fallback to `$HOME/.kube/config` if not set. In this case, the autogenerated RBAC definitions do not need to be applied to the cluster.
+**NOTE:** When running the Helm operator locally, the `run --local` command will default to using the kubeconfig file specified by `$KUBECONFIG` with a fallback to `$HOME/.kube/config` if not set. In this case, the autogenerated RBAC definitions do not need to be applied to the cluster.
 
-Run the `up local` command:
+Run the `run --local` command:
 
 ```sh
-$ operator-sdk up local
+$ operator-sdk run --local
 INFO[0000] Running the operator locally.
 INFO[0000] Go Version: go1.10.3
 INFO[0000] Go OS/Arch: linux/amd64