> My question is, how can I tell to the Configurator bundle to not process > resources that contains placeholder until my ConfigurationPlugin is up?
There are ways that you could attempt to do this, however they’re all inelegant and error prone. What would make more sense would be for the ConfigurationPlugin to detect the existing configurations which contain placeholders at startup and trigger an update for them. This will cause the configuration to be re-delivered, including any necessary configuration plugin execution. In general you are better off trying to make things ordering independent rather than to control the order that things happen in. The result is a much more flexible and stable system. Best Regards, Tim > On 8 Oct 2019, at 12:54, BJ Hargrave via osgi-dev <osgi-dev@mail.osgi.org> > wrote: > > Configuration Plugins mutate configuration data each time it is delivered to > a configuration target. So the Configuration Plugin must be active before any > configuration targets which care about the mutated configuration data. > > So this is orthogonal to Configurator which is about putting configuration > data in the CM configuration data store. > -- > > BJ Hargrave > Senior Technical Staff Member, IBM // office: +1 386 848 1781 > OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 > hargr...@us.ibm.com > > > ----- Original message ----- > From: "Clément Delgrange via osgi-dev" <osgi-dev@mail.osgi.org> > Sent by: osgi-dev-boun...@mail.osgi.org > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> > Cc: > Subject: [EXTERNAL] [osgi-dev] Configurator resources that depend on a > ConfigurationPlugin > Date: Tue, Oct 8, 2019 06:08 > > Hi all, > > I have a question regarding the Configurator and the ConfigurationPlugin > spec. I would like to provision my application with configurations as I do > with my the bundles, for this the Configurator seems perfect. But, the values > inside my configurations could be different depending of the environment > (dev, beta, prod, ...) and my configurations may contain sensitive data that > I don't want in my Git repo. In this case I think I could provide a > ConfigurationPlugin which will replace placeholders with data coming from a > database. > > My question is, how can I tell to the Configurator bundle to not process > resources that contains placeholder until my ConfigurationPlugin is up? > > Thanks, > > Clément Delgrange. > > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > <https://mail.osgi.org/mailman/listinfo/osgi-dev> > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
