[midPoint] Immutable Config / Initial Objects / Overlay

[Pavol Mederly]

I would add my recent experience with this: I had a resource that used 
ScriptedREST connector. This particular connector is not bundled with 
midPoint, so I had to put it into "icf-connectors" subdirectory. 
Unfortunately, the first initial import of the resource always failed, 
because it was executed /before/ the connector discovery process (i.e. 
the resource pointed to a connector that was not loaded yet). Upon 
midPoint restart everything was OK, because the connector was loaded in 
the repository. My (unfinished) overlay project is here 
<https://github.com/Evolveum/iot-story/tree/master/midpoint-iot-overlay>.

If this is your case, we can think of some solution.

(BTW, importing resource via REST API should also work. I think I tried 
it as well, but don't remember the details.)

Best regards,

Pavol Mederly
Software developer
evolveum.com

On 26.08.2016 8:03, Ivan Noris wrote:
> Hi Patrick,
>
> are the objects already perhaps existing in your repository? AFAIK the automatic import feature from initial-objects works only when such objects don't exist in repository yet (that's why it's named "initial"), they will not be overwritten.
> Are you using fixed pre-generated oids for your objects?
> No other idea yet. In my environment, the new objects in initial-objects are being imported upon start - even if I have used this just when midPoint was upgraded and there were new objects provided with the new release. I have not used overlay project yet. Perhaps the other member of this list may have more knowledge in this area.
>
> Best regards,
> Ivan
>
> ----- Original Message -----
>> From: pdbogen at cernu.us
>> To: midpoint at lists.evolveum.com
>> Sent: Friday, August 26, 2016 1:41:44 AM
>> Subject: [midPoint] Immutable Config / Initial Objects / Overlay
>>
>> 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 .
>>              ...
>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20160826/ae1312aa/attachment.htm>