Skip to Main Content
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.
Status Needs review
Categories InterSystems IRIS
Created by Alex Woodhead
Created on Jun 6, 2023

Envrionment variable support in System Default Settings

Docker commonly passes settings via environment variables.

It could be useful if when resolving settings for production configuration this could also evaluate environment variables instead of deployed static values.

Thus the container drives the behavior of the production.

When productions are packaged and deployed the environment variable names are transprted with the export as with static values for production settings.


A suggestion from community is for System Default Settings to:

1) First try using the named environment variable if defined

2) Otherwise fallback to a given "Settings Value"

In first case, the REPORT on what settings are in effect should be expanded to indicate is from Operating System Environment Variable. See attached.

    Jan 24, 2024

    Thank you for submitting the idea. The status has been changed to "Needs review".

    Stay tuned!

  • Admin
    Vadim Aniskin
    Nov 15, 2023

    @Alex Woodhead, you have a comment on your idea. Please answer it to help your idea to be promoted.

    2 replies
  • Steve Pisani
    Jul 28, 2023
    I always felt that it would be good if one could define apart from a value for a setting, an EXPRESSION to call in order to resolve the value. An expression can invoke a method which can look for an environment variable, and also resolve more complex setting values, for example, where your setting needs the production namespace (eg for centralised archiving : archive path = /archives/($ZN)/.. which will work in all deployments, or other run-time specific values.