You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2019/05/24 19:46:00 UTC

[jira] [Resolved] (FELIX-5924) Allow to provide/override config key values using env variables

     [ https://issues.apache.org/jira/browse/FELIX-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-5924.
-------------------------------------
    Resolution: Won't Fix

Its hard to come up with a plugin that works for everyone, therefore the better option is something along the lines of FELIX-6059 which ensures that a specific plugin is running before configurations are handed out

> Allow to provide/override config key values using env variables
> ---------------------------------------------------------------
>
>                 Key: FELIX-5924
>                 URL: https://issues.apache.org/jira/browse/FELIX-5924
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>            Reporter: Christian Schneider
>            Priority: Major
>
> The old configurer allowed to override key/values using env variables. This is very suitable when depolying using docker as it is a standard approach there.
> I propose we also support this for configurator. The data provided in env should override eventual default configs provided inside bundles. 
> If possible we should make sure that the config is still only created once so services do not oscilate.
> With some pointers I might  be able to provide a PR for this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)