container-terminal | Provides a simple container TTY for Kubernetes pods

Required. Either a URL path of the pod as a string, or a Kubernetes resource Pod object. If the latter then ```resource.metadata.selfLink``` will be used as the URL. The name of the container in the Pod to open the terminal for. If not specified then Kubernetes will connect to one of the containers. The command to run. Either an executable string, or an array containing the executable and all the arguments. If not specified will default to running an interactive shell. If set to ```true``` then the widget will not start connecting automatically. It will wait for either user action or for the ```prevent``` flag to be cleared. Reports the connectivity status of the terminal back to the parent scope. The two states currently implemented are ```connected``` and ```disconnected```. This is not an input. There is a container socket service that the terminal widget uses to create the WebSocket objects. The default implementation uses the current document location to qualify the ```pod``` URL.