...
The class is initialized before splicing or desplicing from parser.py and when the init is finished, the instance of TM1SpliceExecutor will have TM1SpliceConfigContainer associated with itself and all configuration files will be already loaded into memory. The configuration data is provided to TM1SpliceExecutor transparently through the TM1SpliceConfigContainer instance (more about the configuration container can be found in Containers (package)
The connection with the TM1 instance is established during the initialization as well.
Splicing
Splicing logic is implemented in splice_cube_rules method and contains following steps.
First, the method will determine TI processes to be run before commencing splicing. The list of processes are configurable and might be added if required to kpi_template.json configuration file to splice_cube_rules object. The list is retrieved from TM1SpliceConfigContainer instance associated with the TM1SpliceExecutor.
Then the method will establish a list of cubes for splicing. The list can be either all cubes as configured in fpm.json in Cubes object, or a list supplied from command line via