-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[v10] Teleport Connect: Add SetGatewayTargetSubresourceName RPC #13884
Conversation
If cliCommand.Env is empty, the returned command has an empty space at the front.
RPCs used to be grouped by action (List/Add/Remove) but I think the longer the list of RPCs gets, the less maintainable this is and it'd be better to group them by resources instead.
Since we want to be able to freely specify the db name after the gateway creation, let's not pass the db name when creating the gateway to show the intent more clearly.
…ceName * cliCommandProvider has been moved from Cluster to Gateway. * Gateway has been modified so that it accepts cliCommandProvider during its creation. * Later it can call cliCommandProvider to get the CLI command when needed. * Setting the CLI command is no longer done outside of Gateway.
This removes the need for SetTargetSubresourceName method on Gateway.
Co-authored-by: rosstimothy <39066650+rosstimothy@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason for not cherry picking just the merge commit?
a7760a4
That's what I'd usually do when backporting PRs manually but it seems that the bot has a different way of doing that. That's also probably why it needs us to not automatically remove the branches after merging. By bot I mean tagging the PR with |
Backport #13476 to branch/v10