[v17] Limit tshd notifications to one per kind per root cluster#62672
Merged
ravicious merged 1 commit intobranch/v17from Jan 7, 2026
Merged
[v17] Limit tshd notifications to one per kind per root cluster#62672ravicious merged 1 commit intobranch/v17from
ravicious merged 1 commit intobranch/v17from
Conversation
* Implement optional key for notifications This necessitated refactoring the state of the service from an array to a map. * Limit tshd notifications to one per kind per root cluster
gzdunek
approved these changes
Jan 7, 2026
avatus
approved these changes
Jan 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport #62031 to branch/v17
changelog: Fixed an issue where Teleport Connect could generate a flurry of notifications about not being able to connect to a resource
Manual backport because of conflicts due to v17 not having #56832.