Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Reconciler update handler to examine old value during update #36171

Merged
merged 1 commit into from
Jan 4, 2024

Conversation

tcsc
Copy link
Contributor

@tcsc tcsc commented Jan 2, 2024

This change allows the Reconciler update handler to examine the existiung
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 2, 2024
@tcsc tcsc requested a review from rosstimothy January 3, 2024 05:44
lib/services/reconciler.go Outdated Show resolved Hide resolved
lib/services/reconciler.go Outdated Show resolved Hide resolved
lib/services/reconciler.go Outdated Show resolved Hide resolved
@tcsc tcsc force-pushed the tcsc/reconciler-gets-old-value branch from c66d3f3 to fb69aa4 Compare January 4, 2024 00:04
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 force-pushed the tcsc/reconciler-gets-old-value branch from fb69aa4 to 8d0518b Compare January 4, 2024 00:17
@tcsc tcsc enabled auto-merge January 4, 2024 00:19
@tcsc tcsc added this pull request to the merge queue Jan 4, 2024
Merged via the queue into master with commit 5a94e3a Jan 4, 2024
33 checks passed
@tcsc tcsc deleted the tcsc/reconciler-gets-old-value branch January 4, 2024 01:13
@public-teleport-github-review-bot

@tcsc See the table below for backport results.

Branch Result
branch/v14 Create PR

Envek added a commit to Envek/teleport that referenced this pull request Jan 4, 2024
…se-anon-key

* origin/master: (344 commits)
  Undelete CreateHostUserMode_HOST_USER_MODE_DROP (gravitational#36273)
  allow cwd to be changed in difftest (gravitational#35946)
  Auth device list component (gravitational#36235)
  make unified resources responsive (gravitational#35961)
  Support running Teleport in a "hot reload" mode (gravitational#35040)
  Prevent deleting enum values, allow deleting enum reservations in types.proto (gravitational#36248)
  Remove support for legacy (Amazon Linux 2) AMIs (gravitational#36153)
  Bump version(s) used for teleport-lab and teleport-quickstart (gravitational#36167)
  Allow Reconciler update handler to examine old value during update (gravitational#36171)
  Validate the user still exists during account reset (gravitational#35676)
  ButtonTextWithAddIcon shared component (gravitational#36103)
  Refactor hostname resolution for SSH connections via the WebUI (gravitational#35773)
  add structuredClone to jest JSDOMEnvironment (gravitational#36213)
  fix flaky `lib/auth` cache-enabled tests (gravitational#36216)
  Report resource usage counts by handling heartbeat events (gravitational#35968)
  Reviewer bot should use the stable version of Go (gravitational#36242)
  RFD 0153 Resource Guidelines (gravitational#34103)
  Use cmp and cmpots properly in operator tests (gravitational#36215)
  Relax Kubernetes CRD discovery when building cache (gravitational#36214)
  Add Access List messages to TAG protobuf (gravitational#36176)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
application-access backport/branch/v14 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.

None yet

3 participants