User reconciliation

[dimitraz]

Description

• Users are initially created in the reconcileRealms() function, as declared in the keycloak.json
• Users that are updated in the realm will be updated again to match the keycloak.json spec
• Users that are modified in the custom resource spec (e.g. via oc or the Openshift console) are updated in the realm to match
• Users in the realm that are not declared in the custom resource will be deleted
• Users in the custom resource that aren't in the realm will be deleted

Verification Verify that the above scenarios behave as expected

To do

• [x] Clean up client api calls in keycloak.go as a lot of duplicate code can be extracted. https://github.com/aerogear/keycloak-operator/pull/22
• [ ] Update spec after user has been created to save the generated ID
• If a user or client field is updated in the keycloak console and that property has not been defined in the keycloak spec it will maintain it. (Expected behaviour would be to delete those fields?)

[mikenairn]

Tested it locally and it does work, although i am seeing issues that i hit as well when doing https://github.com/aerogear/keycloak-operator/pull/23. In particular the use of "omitempty" on all fields is causing some issues.

Also looks like you need to do something similar to what i did here in order to update the spec object with the server side generated user id https://github.com/aerogear/keycloak-operator/pull/23/commits/9093a7838b6eeba277460c02f8382f024648ecaf

[dimitraz]

@mikenairn Updated, can you take another look? I've kept the update function because I think it works nicely and it performs the merge of kc and spec (including booleans) as expected