Discover Wizard: use an already existing DiscoveryService instead of asking user to run one #41688
Labels
discover
Issues related to Teleport Discover
feature-request
Used for new features in Teleport, improvements to current should be #enhancements
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.
The text was updated successfully, but these errors were encountered: