Skip to content

[v14] Allow Reconciler update handler to examine old value during update#36255

Merged
tcsc merged 1 commit intobranch/v14from
bot/backport-36171-branch/v14
Jan 9, 2024
Merged

[v14] Allow Reconciler update handler to examine old value during update#36255
tcsc merged 1 commit intobranch/v14from
bot/backport-36171-branch/v14

Conversation

@tcsc
Copy link
Copy Markdown
Contributor

@tcsc tcsc commented Jan 4, 2024

Backport #36171 to branch/v14

This change allows the Reconciler `onUpdate` handler to examine the existing
value of the resource being reconciled while performing the update. This
allows the handler to take special action for specific changes, for
example locking a user if their upstream identity provider disables the
account.
@tcsc tcsc added the no-changelog Indicates that a PR does not require a changelog entry label Jan 4, 2024
@tcsc tcsc added this pull request to the merge queue Jan 8, 2024
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jan 8, 2024
@tcsc tcsc added this pull request to the merge queue Jan 8, 2024
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jan 9, 2024
@tcsc tcsc added this pull request to the merge queue Jan 9, 2024
Merged via the queue into branch/v14 with commit b3927d2 Jan 9, 2024
@tcsc tcsc deleted the bot/backport-36171-branch/v14 branch January 9, 2024 00:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

application-access backport database-access Database access related issues and PRs desktop-access discovery kubernetes-access no-changelog Indicates that a PR does not require a changelog entry size/sm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants