ClientRef does not update the clientId when it changed/recreated

[nicolamacoir]

I've noticed that when ClientRef is used, it automatically resolves the clientId and stores it in the resource.
However, when the client is recreated and thus the id has changed, this is not updated. The only way to work around this is by manually editing the resources and deleting the clientId - so that it's resolved again and set correctly. This is cumbersome when having many objects pointing to this client. Any suggestions on how to handle this situation?

[vladimirblahoz]

You should be able to use following:

clientIdRef:
      name: {{ $resourceName }}
      policy:
        resolve: Always

[nicolamacoir]

Thanks for the response — that’s really helpful.
Would it make sense to add an option like resolve: ifNotFound? That way, if the clientId isn’t found, it would try resolving again, but avoid re-resolving on every reconciliation. This would improve performance while still handling cases where the client is recreated, without requiring manual updates to all objects with a clientIdRef.

[Breee]

Thanks for the response — that’s really helpful. Would it make sense to add an option like resolve: ifNotFound? That way, if the clientId isn’t found, it would try resolving again, but avoid re-resolving on every reconciliation. This would improve performance while still handling cases where the client is recreated, without requiring manual updates to all objects with a clientIdRef.

I don't know How crossplane implemented that under the hood. We don't have Control over that

[nicolamacoir]

I'm glad to contribute with this, but I'm not sure where to start. Could you point me to any documentation or reference resources that show how these clientIds get resolved?