The best practice is to include a registry export in the same deployment package as all of the cubes that registry contains. That way your portable file is always consistent even if development of the cubes continues.
Once the registry is imported and compiled, use the API
Set status = ##class(%DeepSee.CubeManager.Utils).SetActiveRegistry(className,mustExist)
Direct set of the global will not actually create the updater tasks that do the actual work of managing the automated updates, and the actual location of that global is considered internal and could be subject to change without warning. This API will be maintained for backward compatibility.
If the flag
mustExist = 1
is set then the registry must be compiled and ready before the system will create the updater tasks. This is the default behavior. If
mustExist = 0
and className does not exist, then a new registry will be created and can then be edited in the Cube Registry UI.
All of the task management is done for you automatically when the registry is saved from the Cube Registry page.