InterSystems Ideas
We love hearing from our users. Tell us what you want to see next and upvote ideas from the community.
* Bugs and troubleshooting should as usual go through InterSystems support.
Add a new idea Subscribe
Status Community Opportunity
Categories InterSystems IRIS
Created by Kari Vatjus-Anttila
Created on Jun 30, 2024

RELATED IDEAS

Ability to configure namespace settings and settings outside of CPF merge file capabilities

There should be a way to configure a running instance using a YAML configuration file and / or using a REST API. Currently, a CPF file cannot modify namespace specific settings like schemas, production default settings, credentials and so on. Instead these settings has to be configured manually. I've created a solution already to demonstrate this. The solution can load a YAMLA file that contains settings for a instance and configure a running instance. This is especially useful when used together in CI/CD pipelines and with containers. The solution contains also a REST api that can load properties on a running instance.
  • ADMIN RESPONSE
    Sep 12, 2024

    Thank you for submitting the idea. The status has been changed to "Community Opportunity".

    Stay tuned!

  • Post comment
  • Jani Hurskainen
    Reply
    |     Nov 20, 2024

    We also have similar but very rudimentary internal ObjectScript library that converts JSON configuration into several IRIS ObjectScript API calls. Currently it supports the subset of external service registry, oauth, iop production and task settings we need. It also implements general purpose application configuration pattern all our applications can use (arbitrary JSON configuration is stored into ens lookup table were it can be queried).

  • Kari Vatjus-Anttila
    Reply
    |     Jul 11, 2024
    Yeah, the installation manifest is unsuitable for containerized envs especially ones which use durable %SYS feature. It seems that this might be a thing that is not directly supported at the time being.
  • Corey Hipps
    Reply
    |     Jul 9, 2024

    The closest existing solution is most likely the Installation Manifest.

    This can be used for installation and upgrades.

    I am not certain if it is recommended for container deployments and whether or not improvements could be made for container deployments.

  • Kari Vatjus-Anttila
    Reply
    |     Jul 8, 2024
    Hi Benjamin, Yes, I have. We are currently using CPF:s when deploying to the cloud as well. I'm talking about fine-tuning the instance. For example, adjusting production default settings based on the environment, adding production schemas, credentials, and other namespace-related settings completely automatically. Also, scheduled tasks, configuring OAuth2 servers/clients, and installing and configuring FHIR servers, just to name a few, are out of CPF:s scope, as far as I know. CPF is a great tool to configure the core configuration of an instance, but it cannot be used for fine-tuning a running instance as mentioned earlier. We are currently using a CPF and a separate property file defining these environment-specific fine tunings, which are loaded during deployment asynchronously using a REST API. I'm wondering if a feature like this is wanted by the community and whether we should publish the solution for further testing or not. Let me know if there are existing solutions related to this and whether CPF can alter these setting I mentioned as an example. Thanks, Kari
  • Benjamin De Boe
    Reply
    |     Jul 2, 2024

    Hi Kari,

    have you looked at the Configuration Merge File? This mechanism offers a lot of flexibility for adapting the configuration of a running instance, and is used heavily in our own cloud deployment pipelines.