Tibo Beijen

As janitor iterates all api groups, cleaning those custom resources and then have Helm Operator do the rest, looks like a very good approach. :) ... now only if we...

Second this. In my case at 13: ``` panic: runtime error: index out of range [13] with length 13 ```

It might be worth considering moving the attribute [realm.default_default_client_scopes](https://registry.terraform.io/providers/mrparkers/keycloak/4.4.0/docs/resources/realm#default_default_client_scopes) to a separate resource. Similar to how it is handled on a per-client basis via [keycloak_openid_client_default_scopes](https://registry.terraform.io/providers/mrparkers/keycloak/latest/docs/resources/openid_client_default_scopes) It's easy to hit chicken-egg...

~~It appears as if there is a caching issue in Keycloak. I'm not sure if that's expected behaviour from Keycloak's part~~ It's not caching, it's returning an incomplete `200` instead...

We found out the current provider actively _removes_ any profile and policy that might exist. Even though the fields are 'optional', as stated in the [RealmRepresentation](https://www.keycloak.org/docs-api/22.0.4/rest-api/index.html#RealmRepresentation), and dedicated endpoints exist...