Releases: contiva/cloud-connector-helper
Releases · contiva/cloud-connector-helper
Release list
1.5.0
What's new
Linux: aarch64 and ppc64le support
The Linux scripts (install.sh / update.sh) are no longer limited to x86_64 — they now detect the architecture and use the matching SAP artifacts:
- aarch64 (e.g. AWS Graviton, Azure Ampere) — tested end-to-end on native ARM systems in both archive mode (Debian 12) and RPM mode (Rocky Linux 10). SAP does not publish the SAP JVM for ARM, so the scripts use an existing Java runtime instead (resolved via
JAVA_HOME, a previous SAP JVM install, orjavaonPATH); the archive-mode systemd unit points at the detected runtime. If no runtime is found, the installation aborts with a hint towards SapMachine or the distribution's OpenJDK. The updater reports the JVM as managed outside the helper on ARM. - ppc64le (IBM Power) — implemented symmetrically to x86_64 including the SAP JVM, but untested (no IBM Power hardware available). Feedback welcome.
x86_64 behavior is unchanged (regression-tested).
Full Changelog: 1.4.0...1.5.0
1.4.0
What's new
This release extends the helper suite beyond Linux with dedicated scripts for macOS and Windows.
macOS — install-macos.sh / update-macos.sh
SAP supports the macOS Cloud Connector for development and testing only, and the helpers are designed accordingly:
- Runs entirely without root: installs to
~/sap/cloud-connector(override viaINSTALL_ROOT/SCC_HOME) and manages the Cloud Connector as a per-user launchd agent (com.sap.scc) that starts at login - Apple Silicon native: uses the
macosx-aarch64artifact on ARM Macs andmacosx-x64on Intel; Java is discovered via/usr/libexec/java_home(SCC supports Java 1.8/17/21/25), with a SapMachine hint if none is installed - Supports
--unattended/--accept-eula,--scc-version,--dry-run(exit code 2 when an update is available),--quiet, colored output, install plan, UI readiness check, and config preservation across updates - Tested end-to-end on an Apple Silicon Mac (install, dry-run semantics, update with config preservation and automatic agent restart)
Windows — install-windows.ps1 / update-windows.ps1 ⚠️ not yet verified
- Installs/upgrades the official MSI silently via
msiexec /qn /norestartwith a verbose MSI log in%TEMP%; version detection via the Windows registry; defensive stop/start of the "SAP Cloud Connector" service; UI readiness check - Supports
-Unattended/-AcceptEula,-SccVersion, and-DryRun(exit code 2 when an update is available) - Warning: SAP does not document silent-install MSI properties for the Cloud Connector, and these scripts have not yet been run on a Windows host. Verify on a non-productive machine before rolling out.
Infrastructure
- CI now lints all shell scripts with ShellCheck and the PowerShell scripts with PSScriptAnalyzer
Full Changelog: 1.3.0...1.4.0
1.3.0
What's new
Console UX
- Colored, TTY-aware output: status lines with ✓/! markers, bold section headers,
NO_COLORsupport, and automatic plain output when not running in a terminal. Downloads show a single-line progress bar interactively and stay silent in logs and unattended runs. - Installation plan:
install.shshows the detected system, install mode, versions, and target paths before doing anything; product prompts now default to yes. - Completion panel with readiness check: after installation (and after service restarts during updates), the scripts wait until the administration UI responds on port 8443, then print the URL, credentials, service command, and config path.
- Friendlier errors: blocking processes are listed with their PIDs, download failures hint at proxy settings, and an unknown
--jvm-version/--scc-versionlists the versions that are actually available.
New options
--dry-run(both scripts): show what would happen without changing anything.update.sh --dry-runexits with code2when updates are available and0when up to date — useful for monitoring and cron checks.--quiet(both scripts): package-manager output goes to/var/log/cloud-connector-helper.logwith timestamps and is only shown when a command fails.
Full Changelog: 1.2.0...1.3.0
1.2.0
What's new
Features
- systemd service for archive mode:
install.shnow creates a dedicatedsccadminsystem user and ascc_daemonsystemd unit (enabled and started automatically).update.shstops the service before replacing files, restores ownership, and starts it again afterwards. Without systemd, the manualgo.shstart hint is shown as before. - Unattended installation:
install.sh --unattendedinstalls both products without prompts and requires an explicit--accept-eula. - Version pinning: both scripts accept
--jvm-version <x.y.z>and--scc-version <x.y.z>to install or update to a specific version listed on the SAP tools page. - RPM config backup: before each RPM-mode Cloud Connector update,
configandscc_configunder/opt/sap/sccare backed up to/opt/sap/scc.config-backup(latest backup only).
Reliability
update.shattempts both products even if one fails, prints a final summary, and sends the unattended summary email also when an update fails or the script aborts early.- Archive mode refuses to replace an installation while Cloud Connector processes are still running; the helper-managed service is stopped automatically.
- If extraction fails after the old installation was removed, the config backup is preserved at
<SCC_HOME>.config-backupinstead of being deleted.
Fixes
- README install/update commands now point at the
contivarepository.
Infrastructure
- CI workflow running
bash -nandshellcheckon every push and pull request.
Full Changelog: 1.1.0...1.2.0
1.1.0
What's changed
- Added glibc-based archive install mode for Debian, Ubuntu, and Arch Linux.
- Kept native RPM mode for RHEL/CentOS/Rocky/Alma/Fedora and SUSE/openSUSE.
- Added glibc/platform checks and explicit Alpine/musl rejection.
- Added archive-mode version markers and configuration preservation during SCC archive updates.
- Updated README with a platform support matrix, install modes, and archive start instructions.
Validation
- ShellCheck passed for install.sh and update.sh.
- Docker matrix passed for Fedora, Rocky Linux, AlmaLinux, openSUSE, Debian, Ubuntu, and Arch Linux.
- Alpine was verified as unsupported due to the glibc requirement.
- Debian archive-mode smoke test passed with real SAP downloads and SAPJVM java -version.