[
https://issues.apache.org/jira/browse/FELIX-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618205#comment-16618205
]
Stefan Bischof commented on FELIX-5924:
---------------------------------------
I tried it with ConfigurationPlugin. My ConfigurationBundles requires also the
a Bundle which contains the ConfigurationPlugin.
But how could i know that the Bundle with my ConfigurationPlugin is activated
before any ConfigurationBundles with?
If the ConfigurationPluginBundle starts after the ConfigurationBundles the
ConfigurationPlugin could not replace the config values.
> 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: Configurator
> Affects Versions: configurator-1.0.4
> Reporter: Christian Schneider
> Priority: Major
> Fix For: configurator-1.0.6
>
>
> 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)
