Deployment update CLI parameter workflow_id is defaulted to `update` instead of `None`

Description

In the CLI, when performing a deployment update, the parameter workflow_id's default value is set to "update", which is not really necessary because this default value also exists on the manager if the parameter is not supplied.
It is better that the default value in the CLI will be `None` because when it is not None it means that the user cannot use the flags: skip_install or skip_uninstall, so if the default workflow_id is not None, the user can never supply those flags in the CLI.

Steps to Reproduce

Environment:
CLI of any OS
------------------------------------

Steps to reproduce:
------------------
1. Try to perform a deployment update without supplying a workflow and with at least one of the flags: --skip-install, --skip-uninstall

Expected result:
---------------
A deployment update will be performed.

Actual result:
-------------
The manager returns an error due to supplied both workflow_id and skip_install/skip_uninstall flag.

Why Propose Close?

None

Status

Assignee

Yariv Hamamy

Reporter

Yariv Hamamy

Labels

None

Severity

Medium

Target Version

4.4

Premium Only

no

Found In Version

4.4

QA Owner

Lital Hamami

Bug Type

legacy bug

Customer Encountered

No

Customer Name

None

Release Notes

no

Priority

None

Sprint

None

Fix versions

Priority

Unprioritized
Configure