[midPoint] Immutable Config / Initial Objects / Overlay

[pdbogen at cernu.us]

(With apologies to the moderators, I'm re-sending this now that I'm registered 
to the list; and so hopefully it won't get stuck in moderation.)

Howdy!

I'm trying to get as close as I can to an immutable configuration with 
MidPoint, all baked into a docker container.

I understand that 100% immutable may not be close, but I'd like to have as 
little persistent state as possible -- and more importantly, as little 
involvement as necessary if that state _is_ lost and the whole thing needs to 
get redeployed.

This is a little painstaking since it involves a lot of careful XML changes 
instead of, mostly, using the GUI.

I've run into a bit of an issue, though- to date I've been importing 
everything via Configuration > Import Objects, but I'd like to bundle all my 
objects into the WAR via an overlay.

I have the new WAR being built properly and I can confirm it's including my 
999-blah.xml files in initial-objects, but they don't seem to be applied on 
start.

Is loading a resource in this way supported? If not, is there another easy way 
to import a bunch of objects in automated fashion, perhaps via REST API?

Thanks!
-- 
             .
Patrick Bogen .
            ...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20160826/6fbae87b/attachment.sig>