As your Exalate integration expands you may encounter the need of a centralized version control solution for your scripts, no worries, we got you covered with industry standards.
Custom Git Repository Feature Overview
Github is a platform for code version control and deployment widely used by developers all around the globe, given that Exalate uses a script based console it makes sense that some you might want to use Git to control your Exalate scripts versions.
Exalate provides a solution to integrate Github repositories into the Exalate console by using what we know as “External scripts”. This is basically a library which you can reference inside your Groovy script and import classes from.
Here is an example of a Github repository(ElRepo) which contains a script that we wish to use in the Exalate console(BasicFieldSync.groovy):
This is how the class definition looks on that script:
Given that the node has been correctly configured to access this repository(see notes below) you can then reference it inside the Exalate console as follows:
Once this is implemented I can now make changes to the script rules directly in the Git repository Class script instead of accessing the Exalate console, and enjoy the flexibility that comes with it, along with the version control and other Git features.
Important notes:
-
Theres a 15min update time between changes performed in the git repository to be reflected on the Exalate console itself.
-
Configuration of custom git repo is performed by our cloud team on each node separately.
-
Its possible to configure the node to fetch from private repositories.
-
Example scripts and more information on the scripting side of the action can be found here and here.