[vtadmin] Add cluster protos to discovery and vtsql package constructors #7224
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.
Description
This adds some interface improvements that I immediately regretted not having in the initial PR, namely putting a full Cluster metadata struct in both discovery and vtsql constructors. This allows us to "fix" the problem where we were only passing cluster names (which by design are not necessarily globally unique, so this was a bug) without falling back to a clunkier interface of passing a number of strings (which could change in number (and type!) if we ever add more fields to the cluster proto).
Related Issue(s)
Checklist
Deployment Notes
Impacted Areas in Vitess
Components that this PR will affect: