update wait flag

Signed-off-by: Austin Abro <AustinAbro321@gmail.com>

Author: AustinAbro321

hips/hip-0999.md

@@ -25,7 +25,7 @@ Leveraging a existing status management library maintained by the Kubernetes tea
 
 ## Specification
 
-The Helm CLI will continue to use the existing `--wait` flag. A new flag `--wait-strategy` will be introduced. It will have the options `Watcher` and `legacy`. `--wait-strategy` will default to watcher, which will use kstatus.
+The Helm CLI will continue to use the existing `--wait` flag. The wait flag will be extended to accept `true|false|none|watcher|legacy`. Using `--wait` as flag with no argument, `--wait=true`, or `--wait=watcher` will use the kstatus watcher described in this document. Using `--wait=legacy` will use the current Helm 3 waiter. Using `--wait=false` or not using the `--wait` flag will not avoid waits. 
 
 Kstatus can be used with either a poller or a watcher. The poller runs on a specified interval and only requires "list" RBAC permissions for polled resources. The watcher reacts to [watch events](https://github.com/kubernetes/kubernetes/blob/90a45563ae1bab5868ee888432fec9aac2f7f8b1/staging/src/k8s.io/apimachinery/pkg/watch/watch.go#L55-L61) and requires "list" and "watch" RBAC permissions. This proposal uses the watcher as it responds slightly faster when all resources are ready, and it is very likely that users applying or deleting resources will have "watch" permissions on their resources.