svcat OP does not wait by default. The status will be empty in the output. Useful when you want to chain multiple commands and wait for them later.
svcat OP --wait [--timeout=5m] waits for the instance to be provisioned or fail. Useful for simple scripts that aren't performing concurrent tasks. When a timeout is not set, wait forever.
svcat get RESOURCE --watch mimics the functionality of kubectl. Useful for those who didn't use --wait on the original OP or are watching an operation they didn't initiate from svcat.
Use a slight backoff instead of polling at a set interval. We shouldn't be so aggressive on the backoff that we aren't checking status for huge spans of time. Just enough that we aren't polling every second the entire time.
A pretty common scenario is that I want to execute an operation (provision/bind) and then wait for it to be ready to use.
Lifted from https://github.com/Azure/service-catalog-cli/pull/83#discussion_r158100654
svcat OPdoes not wait by default. The status will be empty in the output. Useful when you want to chain multiple commands and wait for them later.svcat OP --wait [--timeout=5m]waits for the instance to be provisioned or fail. Useful for simple scripts that aren't performing concurrent tasks. When a timeout is not set, wait forever.svcat get RESOURCE --watchmimics the functionality ofkubectl. Useful for those who didn't use--waiton the original OP or are watching an operation they didn't initiate from svcat.