Question
· Jul 24

How to handle Ens.Config.DefaultSettings() with IPM

#InterSystems Package Manager (IPM) #InterSystems IRIS for Health

I feel I may be in the "people unclear on the concept" group here.

System Default Settings is a great mechanism, and we use some custom code to deploy it in our pipeline after environment specific changes have been applied to the content. However, we are trying our best to reduce the amount of custom code we use in our system that does not relate directly to the business. For CI/CD, this means we are trying to leverage IPM for the heavy lifting.

Is there a method for handling System Default Settings in IPM that I am just overlooking? If not, what would be a good approach that would not involve custom extensions of the IPM code? Invoke would be fine, but I want to make sure I am not missing something obvious here.

Thanks in advance for your opinions!

-Jonathan

Product version: IRIS 2025.1
Discussion (4)3
Log in or sign up to continue
DC AI Bot · Jul 24

There is no direct documentation or feature in InterSystems Package Manager (IPM) that specifically addresses handling System Default Settings for CI/CD pipelines. However, here are potential approaches based on available information:

  1. System Default Settings: These settings simplify management of environment-specific configurations, such as file paths, port numbers, etc., and can be exported/imported using methods like %Export and %Import. It is advisable to integrate these methods into your pipeline processes to automate these tasks [1][2].

  2. Custom Automation: While not directly tied to IPM, you can use tools or scripts, such as the GetSettingsFromProduction method, to gather and setup System Default Settings efficiently during the deployment process. This method allows filtering specific settings and automating their migration to the system defaults table [3][4].

  3. Source Control: System Default Settings can be exported and tracked in version control. Each branch or CI/CD environment can include specific setting files, which can then be applied programmatically during deployment [2].

If Invoke scripts are acceptable for your case or specific automation needs, they could wrap around these export/import or automation methods to ensure smooth integration without extending IPM itself. For completely eliminating custom solutions, consider submitting a feature enhancement request on InterSystems Developer Community.

Sources:

0 0