feature: Import objects via <realm/name> instead of <uuid>

[Breee]

Currently we have to import resources using keycloaks UUIDs,
i.e.

apiVersion: role.keycloak.crossplane.io/v1alpha1
kind: Role
metadata:
  annotations:
    crossplane.io/external-name: 182b0c9b-197f-45e3-8f4a-386cd6890d73
  name: builtin-master-realm-role-uma-authorization
spec:
  deletionPolicy: Orphan
  forProvider:
    name: uma_authorization
    realmId: master
  managementPolicies:
  - Observe
  providerConfigRef:
    name: keycloak-provider-config

It would be better to have something like:

apiVersion: role.keycloak.crossplane.io/v1alpha1
kind: Role
metadata:
  annotations:
    crossplane.io/external-name: master/uma_authorization
  name: builtin-master-realm-role-uma-authorization
spec:
  deletionPolicy: Orphan
  forProvider:
    name: uma_authorization
    realmId: master
  managementPolicies:
  - Observe
  providerConfigRef:
    name: keycloak-provider-config

to make it more resilient for disaster recovery

[TomBillietKlarrio]

I was wondering, what would be the behavior if in external_name.go the config is changed to config.NameAsIdentifier

provider-keycloak/config/external_name.go

Line 26 in 9be1e15

"keycloak_openid_client": config.IdentifierFromProvider,

Would it try to reconcile based on the name instead of the UUID? I was trying it myself, but did not figure out how to run a custom built version on my kind cluster

[Breee]

afaik config.NameAsIdentifier would remove all "name" fields from the forProvider and use the K8s object name as identifier.
that's not what we search i think -> we'll find a smooth way to get rid of the uuids in the future. To this date this does not exist.