Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5464

Add environment variables as a source for model expression resolution

    XMLWordPrintable

Details

    Description

      As the cloud relies more on container env vars than system properties, we should allow for transparent resolution of expressions
      from env vars as well as the current system property mechanism.

      For example, if I have the following xml

      <element some-attribute="${test.my-property:default}"/>

      At present you need to start the server with -Dtest.my-property=hello (or via a model entry for the property) to replace the value at runtime.

      This RFE proposes that if the env var TEST_MY_PROPERTY=hola is set when starting the server, we use the value of the environment variable.

      To keep this similar to how MP Config does the same thing, the system property will take precedence over the environment variable if defined.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users DMR-45 Resolve env variables without requiring a env. prefix

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is documented by

          Feature Request - Feature requests from customers and/or users WFLY-14899 Document: Add environment variables as a source for model expression resolution

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-5562 Upgrade JBoss DMR 1.6.1.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. ELY-2389 Consistent expression resolution with WildFly

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              kkhan1@redhat.com Kabir Khan
              kkhan1@redhat.com Kabir Khan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: