During reconciliation of applicationAuth, when the initial reconciliatino is done and value of user_key has been updated, if applicationAuth CR is removed and re-created with just a new user_key value, the operator updates the user_key but fails on subsequent call.
This causes operator to keep reconiciling applicaitonAuth indefinitely and pushes the token on every reconcile, which means that even if user decided to update the token via ui/api, the token would get reverted. This is a problem because the functionality is entirely different when there is no error in reconciler vs when there is an error.
We should find a common ground on how we handle error/successful reconciliation and stick to it.