Legacy clone engine scripting enters EoL

We are excited to announce that the legacy clone engine scripting libraries and utilities, including:

Core Libraries: Boot.lib, File.lib, Inventory.lib, PostConf.lib, Registry.lib, System.lib, Cache.lib, FileSystem.lib, Net.lib, Protocol.lib, Rsync.lib, Disk.lib, Image.lib, PostConfEAC.lib, String.lib, UEFI.lib, and ImagenesSincronizadas.lib

Standalone Scripts: bootLinux, bootOs, bootOsCustom.template, bootWindows, buildToOrder, cloneRemoteFromMaster, configureOs, configureOsCustom.template, createBaseImage, createDiffImage, createImage, createImageCustom.template, createLogicalPartitions, createPrimaryPartitions, deployImage, formatFs, generateMenuDefault, getFsType, getIpAddress, getOsVersion, grubSyntax, poweroff, README.es.txt, reboot, remoteConsole, restoreBaseImage, restoreDiffImage, restoreImage, restoreImageCustom.template, installOfflineMode, launchOgagentInstaller, listHardwareInfo, listPartitions, listPrimaryPartitions, listSoftwareInfo, menuBrowser, ogCrearImagenBasica, ogCrearSoftIncremental, ogRestaurarImagenBasica, ogRestaurarSoftIncremental, runAplicationX.sh, runhttplog.sh, sendFileMcast, setBootMode, updateBootCache, updateCache, and related utilities are officially discontinued in favor of our new and improved Scripting Infrastructure.

🚀 What's New: Post-Configuration & Custom Scripting

The new infrastructure simplifies automation and gives you flexible, organized control over post-deployment tasks using standard scripting languages.

Post-Configuration Scripts* store and execute custom scripts that run automatically after image restoration:

  • Live environments: /opt/opengnsys/client/postconf/live. Place your Bash scripts here for execution in live mode. These scripts are run after the image restoration.
  • Windows environments: /opt/opengnsys/client/postconf/windows. Place your .ps1 PowerShell or .cmd Batch files here. These scripts are run in the first boot of this OS in the mini-setup mode.

Access these scripts directly from ogCP: Images → Edit Images Then, select the scripts that you want to run after the image restoration.

  • On-Demand Custom Scripts: Run ad-hoc maintenance, diagnostics, or configuration tasks anytime. Universal script directory: /opt/opengnsys/client/shell/. Store reusable Bash, PowerShell, or other compatible scripts here for Linux and Windows environments.

Access these scripts from ogCP: Commands → Run → Run Scripts

  • Scripting Environment Variables: To facilitate dynamic scripting, specific environment variables are automatically injected into your scripts during execution: OG_DEVICE_PATH (Bash): This variable is set automatically in Bash scripts and specifies the /dev path to the partition where an image is being restored (e.g., /dev/sda1). You can use this variable directly in your scripts to target the correct device without hardcoding paths.

✅ Benefits of the New Infrastructure

  • Clean separation of concerns: post-conf vs. on-demand execution
  • Native support for Bash, PowerShell, and CMD syntax
  • Dynamic Device Handling: Use OG_DEVICE_PATH to safely identify target partitions from your scripts
  • Integrated visibility and management through ogCP

📅 Support Timeline

Legacy scripting support will continue until August 2026. After this date, legacy libraries and scripts will no longer receive updates, testing, or technical support.

🔁 Migration Guidance

We strongly encourage all users to begin transitioning their workflows to the new scripting infrastructure now. Start by:

  • Replace your existing PostConf.lib based custom script logic.
  • Refactoring tasks into Bash (.sh) or PowerShell (.ps1) files. Utilizing OG_DEVICE_PATH in Bash scripts to handle partition targeting dynamically.
  • Placing them in the appropriate directory (postconf/live, postconf/windows, or shell/).
  • Testing execution via ogCP before decommissioning legacy calls.
  • Comprehensive migration examples and best practices are available in our updated documentation portal.

🆘 Need Assistance?

If you have questions about adapting your automation workflows, need help converting legacy script logic, or want guidance on structuring new post-configuration tasks, our support team at opengnsys@soleta.eu is here to help.

Thank you for being part of our community and for your continued trust in our solutions. We're committed to empowering you with more flexible, maintainable, and powerful tools for your imaging and deployment operations.