Skip to content

Support opening the Query Editor from outside (Portal, Fabric) using registerUriHandler #2532

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

Open
sevoku opened this issue Jan 13, 2025 · 0 comments · May be fixed by #2635
Open

Support opening the Query Editor from outside (Portal, Fabric) using registerUriHandler #2532

sevoku opened this issue Jan 13, 2025 · 0 comments · May be fixed by #2635

Comments

@sevoku
Copy link
Member

sevoku commented Jan 13, 2025

We want to add "Open in VS Code" buttons to the Azure Portal and Fabric, for this we need to implement a handler using vscode.window.registerUriHandler (on activation) which will open the selected database/container in the Query Editor.

Ideally we would detect whether the resource exists in the Azure Resources tree and navigate to there, however that's currently not supported by the Tree View API.

The simplest approach (per offline discussion) is to support following Uri parameters:

  • connection string (can support any database type)
    • we should be able to detect which database SDK it is (NoSQL/Mongo) and act accordingly
  • Database Name
  • Container Name

Following actions would be taken:

  • Look up if an Attached Account with the same connection string exists
    • Add an "Attached Account" entry if not
    • Expand the node
  • Open the Query editor for the given database and collection
@sevoku sevoku added the feature label Jan 13, 2025
@sevoku sevoku added this to the 0.25.0 milestone Jan 13, 2025
@sevoku sevoku changed the title Support opening the Query Editor from outside (Portal, Fabric) suing registerUriHandler Support opening the Query Editor from outside (Portal, Fabric) using registerUriHandler Jan 13, 2025
@tnaum-ms tnaum-ms modified the milestones: 0.25.0, 0.26.0 Feb 18, 2025
@sevoku sevoku self-assigned this Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment