feat: filter accounts by egress node or subscription source - #834
Merged
Conversation
feat: filter accounts by egress node or subscription source The account list could only split proxy bindings into bound and unbound. Operators troubleshooting one proxy exit or one subscription had no way to see just the accounts sitting behind it. The bound branch of the proxy-binding filter now opens a third menu level listing every egress node and every subscription source that can serve the current account pool, so the options re-scope as the list switches between Grok Build, Web and Console. The egress query value carries the narrowing: "node:<id>" and "source:<id>" both mean bound, restricted to one node or to every node owned by one subscription. Invalid targets are rejected as an invalid filter.
MMortise
changed the title
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
2 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.
The account list could only split proxy bindings into bound and unbound.
Operators troubleshooting one proxy exit or one subscription had no way to
see just the accounts sitting behind it.
The bound branch of the proxy-binding filter now opens a third menu level
listing every egress node and every subscription source that can serve the
current account pool, so the options re-scope as the list switches between
Grok Build, Web and Console.
The egress query value carries the narrowing: "node:" and "source:"
both mean bound, restricted to one node or to every node owned by one
subscription. Invalid targets are rejected as an invalid filter.