This commit extends the sw-deploy-strategy API to support a new
`with-prestage` parameter. When set, the sw-deploy orchestration
will automatically execute a prestage if it has not been performed
already, ensuring the environment is prepared before deployment.
To enable this functionality, the API schema and validation logic
are updated to accept `with-prestage` along with the additional
parameters required for prestage: `sysadmin_password` and `force`.
This also adds a restriction when the new parameter is used, limiting
the max-parallel-subclouds value to 250.
Test Plan:
PASS: Create a sw-deploy-strategy via API with `with-prestage=true`
and verify prestage runs when not previously executed.
PASS: Create a sw-deploy-strategy with `with-prestage=true` when
prestage has already been completed, and verify no duplicate
prestage runs occur.
PASS: Validate API rejects invalid or missing `sysadmin_password`
when `with-prestage` is requested.
PASS: Confirm that `force` parameter is properly passed to the
prestage orchestration when set.
PASS: Validate --max-parallel-subclouds parameter for strategy
creation and subcloud-group add, for default limit (5000)
and prestage limit (250)
Story: 2011552
Task: 52898
Change-Id: Ie0fe098740fa29352e22099be4146f55087b09f3
Signed-off-by: Hugo Brito <hugo.brito@windriver.com>