Do not delete Keycloak items on Kubernetes object deletion by default

[julianbuettner]

Is your feature request related to a problem? Please describe.
I just renamed the KeycloakRealm object and accidentally deleted the staging realm.
(renaming + kubectl apply = delete + create?)
There were backups in place, so everything turned out fine, but it's a hell of a trap to fall in.

Describe the solution you'd like
I would like to not have my realms deleted.
Maybe an annotation like delete-keycloak-object-on-kubernetes-deletion with a default of false,
which has to be explicitly set to true to keep the current behaviour. Examples could be updated, so the issue is
directly recognized by users not thinking much (like me).

(Compare "helm.sh/resource-policy": "keep")

Describe alternatives you've considered
Not using this product, because it contains a rather big footgun.
But I would like to use it in production, because it's otherwise exactly what I need.

Additional context
N/A

[SergK]

@julianbuettner Hello, I think we can make this field immutable and not allow such operations but force the user to create a new realm. @zmotso, what do you think? Since Keycloak API doesn't allow such stuff, recreation operations can be dangerous.

[zmotso]

@SergK @julianbuettner Hi. Yes, we can add some annotation/parameter to the CR to prevent deletion of the realm. We can implement it shortly (in a week or two).

[julianbuettner]

It would be great to have it for other (all?) object kinds as well, like KeycloakUser, KeycloakClient, etc, not just KeycloakRealm.
Although for KeycloakRealm I would need it the most.

[julianbuettner]

It appears to me the issue is fixed, so I will close this issue now.
Thank you for implementing this request.
Is there an estimated time of the next release?

[SergK]

@julianbuettner, please expect till the end of this week.