As for the sensitive settings in the properties XML/cfg files, I'd probably
go this way:
On Fri, Sep 16, 2016 at 12:34 PM, Brad Johnson <brad.john...@mediadriver.com
> I've tried to find ways to override the values of a pid, though haven't
> dug into it in depth. Also the possibility of using multiple pids in a
> single blueprint (achieving much the same.)
> Theoretically it is possible and I think it is in DS but I'm not a big
> user of DS so don't take that as gospel. I think even blueprint permits
> but the problem is in the implementation (again don't quote me on that
> one.) My recollection is that it should be possible but the Camel blueprint
> and Aries of at least some earlier versions didn't support it. I've become
> so used to using a single PID that I don't worry about it. One solution is
> you can create an OSGi service for the functionality that is required by
> and shared between the bundles and call that service instead of duplicating
> it across bundles.
> On Fri, Sep 16, 2016 at 4:20 AM, owain <email@example.com>
>> Thanks for the tip. I have a parent project (POM) and modules, one each
>> services. So currently I have a pid for each service but some of the cfg
>> settings are common across projects (e.g. kafka server address which is a
>> pointer to a docker linked container).
>> What would be cool would be to have some defaults in a parent pid and then
>> over-rides and additional ones in the modules pid (or same pid?). Is
>> a way to do this?
>> Additionally, some of the properties should not be in git since they are
>> "secure". At the moment I am deploying them via a volume mount from the
>> fuse docker container to /etc and intend to manage them via a fabric
>> (next stage). Any tips on this.
>> A very useful reply, might be a blog post? Only the basics are covered in
>> the Camel in Action and Cookbook.
>> Thanks again.
>> View this message in context: http://camel.465427.n5.nabble.
>> Sent from the Camel - Users mailing list archive at Nabble.com.