Repository controller doesn't update ressource on password change
wotolom opened this issue · 2 comments
What happened?
The isUpToDate method does not check if the password provided via secret changed.
The workaround is currently to trigger an update-call by changing another field in the repo claim.
How can we reproduce it?
Deploy secret with e.g. token, deploy repo referencing the secret (see example).
Write a new token in the secret or reference another secret with a new token.
-> no update call/request + new token is not being used
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 7 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.
/fresh
I would like to contribute to this issue.