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

Discover Wizard: use an already existing DiscoveryService instead of asking user to run one #41688

Open
marcoandredinis opened this issue May 17, 2024 · 0 comments
Labels
discover Issues related to Teleport Discover feature-request Used for new features in Teleport, improvements to current should be #enhancements

Comments

@marcoandredinis
Copy link
Contributor

What would you like Teleport to do?
When going through the Discover wizard, that requires a DiscoveryService, teleport should lookup any existing DiscoveryServices that might be running and re-use them instead of asking the user to run one themselves.
The wizard must pick one of the existing DiscoveryService's DiscoveryGroup to use when creating the DiscoveryConfig.

What problem does this solve?
Improves UX (one less step) and reduces required operations

If a workaround exists, please include it.

@marcoandredinis marcoandredinis added feature-request Used for new features in Teleport, improvements to current should be #enhancements discover Issues related to Teleport Discover labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discover Issues related to Teleport Discover feature-request Used for new features in Teleport, improvements to current should be #enhancements
Projects
None yet
Development

No branches or pull requests

1 participant