We would like to have the ability to create local (Immy tenant-specific) deltas of global software items in Immybot. This feature would enable users to create a fork of global software items within their tenant while maintaining the core installation scripts, parameters, config scripts, etc. provided by Immybot. Users would also be able to upload their own updated installer files when the global software hasn’t been updated yet. In addition, in some scenarios, we might want to use a differing install or configuration script or add additional parameters.
Example Scenario:
For instance, the latest global version of the Egnyte Desktop App in Immybot might be 3.16, but newer versions like 3.19 are already available. Instead of requesting Immybot support to update the global item, users should be able to create a local fork of the global item (in this case, Egnyte Desktop App 3.16) and upload the latest version (3.19) for their specific tenant. The local fork would continue utilizing the same global install script, ensuring consistency in deployment while allowing tenants to manage their updates.
Current Workflow vs Suggested Improvement:
Currently, we can manually re-create the global software as a local software, make any necessary edits to the installation script, and upload new software versions. However, this process can be time-consuming and less efficient.
Proposed Benefits:
- Improved Efficiency: Reduces the dependency on Immybot support for global software updates.
- Faster Software Updates: Allows tenants to adopt the latest software versions more quickly.
- Streamlined Process: Maintains consistency by reusing global install scripts while allowing version flexibility for local tenant needs.
This feature would significantly enhance flexibility and reduce administrative overhead when managing software versions across tenants.