Command line support for single virtual machine installation

Base syntax:

sudo ./AppScan360_SingleVMsetup_v<version>.run -- <kits_location> [option]

or

sudo ./AppScan360_SingleVMsetup_v<version>.run -- <kits_location> [parameter]

Run the installer without any option when you want the normal guided installation flow for:

• a new full installation (express or custom), and,
• you do not need modular recovery, upgrade, backup, or maintenance utilities.

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD

To run the installation in smaller controlled steps because:

• a previous installation failed and you want to recover in steps.
• you want to install only one component.
• you want to resume installation from a selected component.

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD --modular

To run the supported upgrade path when an AppScan 360° deployment already exists:

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD --upgrade

To export persistent volume data before upgrade or maintenance:

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD --backup

Typical backup files are ascp-pv-<timestamp>.tar.gz and sca-pv-<timestamp>.tar.gz.

Base format:

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD <parameter>

To create the certificate folder structure under <kits_location>/certs when you plan to provide custom or self-signed certificates before installation:

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD prepareCertsFolders

The command creates folders for:

• Docker registry certificates
• LDAP certificates
• SMTP certificates
• OIDC certificates
• OpenTelemetry certificates I
• ngress/Application domain certificates

To update storage ownership for the 1.6.x to 2.x.x upgrade path when following the documented upgrade steps.

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD updateStorageOwnership

To prepare an existing deployment for the Gateway API and Istio based upgrade path when you need to remove older ingress-nginx and cert-manager components before continuing the upgrade.

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD prepareUpgrade

This command:

• removes ingress-nginx.
• removes old cert-manager.
• deletes existing Ingress resources in hcl-appscan-ascp.
• cleans up older cert-manager CRDs.

After this step, rerun the installer to continue the upgrade.

To run a targeted remediation for known post-upgrade storage issues when the ascp-mr-tasks-manager pod does not recover after upgrade because of the known storage issue:

sudo ./AppScan360_SingleVMsetup_v<version>.run -- $PWD remediateStorageIssues

This command:

• corrects storage permissions.
• clears the affected storage content under the SAST tools path.
• restarts the tasks manager pod.

If the installer detects an existing ASCP deployment and you start the normal fresh-install flow, it stops and tells you to rerun with:

• --upgrade for upgrade flow.
• --modular for controlled component-wise flow.

If a previous engage log is found and you start the regular flow, the installer asks whether to continue from the last successful step.

• If you choose Yes, it switches to modular mode.
• If you choose No, it continues with the regular installation flow.
• In non-interactive mode, it defaults to modular mode.