Are you using v2Archive enRoute or the new one? The v2Archive OSGi enRoute has the simple Configurer (the predecessor of the OSGi R7 Configurator but with, according to some, a better name :-). It runs things through the macro processor you could therefore use environment variables to make the difference.
E.g. ${env;XUZ} in the json files. Since it also supports ${if} you can eat
your heart out! You can set environment variables in docker with -e in the
command line when you start the container. You can also use @{ instead of ${ to
not run afoul of the bnd processing that can happen at build time. I.e. the
Configurer replaces all @{…} with ${…}.
If you are using the new R7 Configurator then you are on your own ...
Kind regards,
Peter Kriens
> On 18 Aug 2018, at 18:51, Randy Leonard via osgi-dev <[email protected]>
> wrote:
>
> To all:
>
> We are at the point where we are deploying our OSGI enRoute applications via
> Docker.
>
> - A key sticking point is the syntax for embedding environment variables
> within our configuration.json files.
> - For example, a developer would set a hostName to ‘localhost’ for
> development, but this same environment variable would be different for QA,
> UAT, and Production environments
> - I presume this is the best way of allowing the same container to be
> deployed in different environments without modification?
> - Suggestions and/or examples are appreciated.
>
>
>
> Thanks,
> Randy Leonard
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
