Automating Control Center (CC) installation and configuration externally parameters to pass

Currently, during the execution of configCC.sh, configuration parameters are typically provided in interactive mode, or they are read from the static configuration script runConfigCCSample.sh, where values are hardcoded.

For automation purposes, there is a need to externally pass configuration parameters as variables at runtime instead of relying solely on the values defined inside runConfigCCSample.sh.

Enabling this capability would allow the installation process to accept parameters dynamically, for example:

./runConfigCCSample.sh TRUSTSTORE="/app/truststore.jks"

This approach will help automate the installation process by allowing deployment tools or scripts to override specific parameters while still using the default configuration defined in runConfigCCSample.sh.

Benefits:

1. Eliminates the need to manually modify configuration scripts for each environment.

2. Enables fully automated deployments across environments such as DEV, QA, and PROD.

3. Improves deployment consistency and reduces human errors.

4. Simplifies integration with automation frameworks and CI/CD pipelines.

5. Allows reuse of the same base configuration script with environment-specific overrides.

6. This enhancement will make Control Center installations more flexible, repeatable, and automation-ready, supporting the broader objective of standardizing and automating SDE deployments