Rollback a release to the specified revision


werf helm rollback RELEASE_NAME REVISION [options]


            Allow deletion of new resources created in this rollback when rollback failed
            Force resource update through delete/recreate if needed
            Helm release storage namespace (same as --tiller-namespace for regular helm, default    
            helm storage driver to use. One of 'configmap' or 'secret' (default                     
            $WERF_HELM_RELEASE_STORAGE_TYPE or 'configmap')
  -h, --help=false
            help for rollback
            Use specified dir to store werf cache files and dirs (default $WERF_HOME or ~/.werf)
            Kubernetes config file path (default $WERF_KUBE_CONFIG, or $WERF_KUBECONFIG, or         
            Kubernetes config data as base64 string (default $WERF_KUBE_CONFIG_BASE64 or            
            Kubernetes config context (default $WERF_KUBE_CONTEXT)
            Set log color mode.
            Supported on, off and auto (based on the stdout’s file descriptor referring to a        
            terminal) modes.
            Default $WERF_LOG_COLOR_MODE or auto mode.
            Enable debug (default $WERF_LOG_DEBUG).
            Enable emojis, auto line wrapping and log process border (default $WERF_LOG_PRETTY or   
            Disable explanatory output (default $WERF_LOG_QUIET).
            Set log terminal width.
            Defaults to:
            * interactive terminal width or 140
            Enable verbose output (default $WERF_LOG_VERBOSE).
            Prevent hooks from running during rollback
            Perform pods restart for the resource if applicable
            Max releases to keep in release storage. Can be set by environment variable             
            $WERF_RELEASES_HISTORY_MAX. By default werf keeps all releases.
            Time in seconds to wait for any individual Kubernetes operation (like Jobs for hooks)
            Use specified dir to store tmp files and dirs (default $WERF_TMP_DIR or system tmp dir)
            If set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a       
            Deployment are in a ready state before marking the release as successful. It will wait  
            for as long as --timeout