Skunktendo 2024: automatically detect Local Atlas #731
Conversation
This file contains 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
With this PR, the VS Code extension detects local atlas environments and shows them in the list of connections so that the user does not need to pass connection strings around. It does so by looking at the running docker containers, as that is how local atlas environments are provided. As added bonus, connections can now be open in Compass directy from VSCode if the protocol handler is registered.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With this PR, the VS Code extension detects local atlas environments and shows them in the list of connections so that the user does not need to pass connection strings around.
It does so by looking at the running docker containers, as that is how local atlas environments are provided.
As added bonus, connections can now be open in Compass directy from VSCode if the protocol handler is registered.
Description
Wouldn't it be nice if our dev tools delivered a unified developer experience? This is what I could come up with in the couple of free hours I had this week.
Checklist
Motivation and Context
Open Questions
Dependents
Types of changes