@@ -8469,8 +8469,6 @@ _oc_deploy()

     flags_with_completion=()

     flags_completion=()

-    flags+=("--enable-triggers")

-    local_nonpersistent_flags+=("--enable-triggers")

     flags+=("--follow")

     local_nonpersistent_flags+=("--follow")

     flags+=("--retry")

@@ -11895,6 +11893,7 @@ _oc_rollout_cancel()

     flags+=("--match-server-version")

     flags+=("--namespace=")

     two_word_flags+=("-n")

+    flags+=("--request-timeout=")

     flags+=("--server=")

     flags+=("--token=")

     flags+=("--user=")

@@ -13094,8 +13094,6 @@ _openshift_cli_deploy()

     flags_with_completion=()

     flags_completion=()

-    flags+=("--enable-triggers")

-    local_nonpersistent_flags+=("--enable-triggers")

     flags+=("--follow")

     local_nonpersistent_flags+=("--follow")

     flags+=("--retry")

@@ -16564,6 +16562,7 @@ _openshift_cli_rollout_cancel()

     flags+=("--match-server-version")

     flags+=("--namespace=")

     two_word_flags+=("-n")

+    flags+=("--request-timeout=")

     flags+=("--server=")

     flags+=("--token=")

     flags+=("--user=")

@@ -8630,8 +8630,6 @@ _oc_deploy()

     flags_with_completion=()

     flags_completion=()

-    flags+=("--enable-triggers")

-    local_nonpersistent_flags+=("--enable-triggers")

     flags+=("--follow")

     local_nonpersistent_flags+=("--follow")

     flags+=("--retry")

@@ -12056,6 +12054,7 @@ _oc_rollout_cancel()

     flags+=("--match-server-version")

     flags+=("--namespace=")

     two_word_flags+=("-n")

+    flags+=("--request-timeout=")

     flags+=("--server=")

     flags+=("--token=")

     flags+=("--user=")

@@ -13255,8 +13255,6 @@ _openshift_cli_deploy()

     flags_with_completion=()

     flags_completion=()

-    flags+=("--enable-triggers")

-    local_nonpersistent_flags+=("--enable-triggers")

     flags+=("--follow")

     local_nonpersistent_flags+=("--follow")

     flags+=("--retry")

@@ -16725,6 +16723,7 @@ _openshift_cli_rollout_cancel()

     flags+=("--match-server-version")

     flags+=("--namespace=")

     two_word_flags+=("-n")

+    flags+=("--request-timeout=")

     flags+=("--server=")

     flags+=("--token=")

     flags+=("--user=")

@@ -16,11 +16,7 @@ oc rollout cancel \- cancel the in\-progress deployment

 Cancel the in\-progress deployment

 .PP

-Running this command will cause the current in\-progress deployment to be

-cancelled, but keep in mind that this is a best\-effort operation and may take

-some time to complete. It’s possible the deployment will partially or totally

-complete before the cancellation is effective. In such a case an appropriate

-event will be emitted.

+Running this command will cause the current in\-progress deployment to be cancelled, but keep in mind that this is a best\-effort operation and may take some time to complete. It’s possible the deployment will partially or totally complete before the cancellation is effective. In such a case an appropriate event will be emitted.

 .SH OPTIONS

@@ -87,6 +83,10 @@ event will be emitted.

     If present, the namespace scope for this CLI request

 .PP

+\fB\-\-request\-timeout\fP="0"

+    The length of time to wait before giving up on a single server request. Non\-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.

+

+.PP

 \fB\-\-server\fP=""

     The address and port of the Kubernetes API server

@@ -103,7 +103,7 @@ There are several deployment strategies defined:

 .SH SEE ALSO

 .PP

-\fBoc(1)\fP, \fBoc\-rollout\-history(1)\fP, \fBoc\-rollout\-latest(1)\fP, \fBoc\-rollout\-pause(1)\fP, \fBoc\-rollout\-resume(1)\fP, \fBoc\-rollout\-status(1)\fP, \fBoc\-rollout\-undo(1)\fP,

+\fBoc(1)\fP, \fBoc\-rollout\-cancel(1)\fP, \fBoc\-rollout\-history(1)\fP, \fBoc\-rollout\-latest(1)\fP, \fBoc\-rollout\-pause(1)\fP, \fBoc\-rollout\-resume(1)\fP, \fBoc\-rollout\-status(1)\fP, \fBoc\-rollout\-undo(1)\fP,

 .SH HISTORY

@@ -16,11 +16,7 @@ openshift cli rollout cancel \- cancel the in\-progress deployment

 Cancel the in\-progress deployment

 .PP

-Running this command will cause the current in\-progress deployment to be

-cancelled, but keep in mind that this is a best\-effort operation and may take

-some time to complete. It’s possible the deployment will partially or totally

-complete before the cancellation is effective. In such a case an appropriate

-event will be emitted.

+Running this command will cause the current in\-progress deployment to be cancelled, but keep in mind that this is a best\-effort operation and may take some time to complete. It’s possible the deployment will partially or totally complete before the cancellation is effective. In such a case an appropriate event will be emitted.

 .SH OPTIONS

@@ -87,6 +83,10 @@ event will be emitted.

     If present, the namespace scope for this CLI request

 .PP

+\fB\-\-request\-timeout\fP="0"

+    The length of time to wait before giving up on a single server request. Non\-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.

+

+.PP

 \fB\-\-server\fP=""

     The address and port of the Kubernetes API server

@@ -103,7 +103,7 @@ There are several deployment strategies defined:

 .SH SEE ALSO

 .PP

-\fBopenshift\-cli(1)\fP, \fBopenshift\-cli\-rollout\-history(1)\fP, \fBopenshift\-cli\-rollout\-latest(1)\fP, \fBopenshift\-cli\-rollout\-pause(1)\fP, \fBopenshift\-cli\-rollout\-resume(1)\fP, \fBopenshift\-cli\-rollout\-status(1)\fP, \fBopenshift\-cli\-rollout\-undo(1)\fP,

+\fBopenshift\-cli(1)\fP, \fBopenshift\-cli\-rollout\-cancel(1)\fP, \fBopenshift\-cli\-rollout\-history(1)\fP, \fBopenshift\-cli\-rollout\-latest(1)\fP, \fBopenshift\-cli\-rollout\-pause(1)\fP, \fBopenshift\-cli\-rollout\-resume(1)\fP, \fBopenshift\-cli\-rollout\-status(1)\fP, \fBopenshift\-cli\-rollout\-undo(1)\fP,

 .SH HISTORY