Extension API: triggering kernel selection for a specific JupyterServer

[amtoney524]

hi! I'm wondering if there's a way to programmatically trigger the kernel selector for a specific JupyterServer (e.g., via executeCommand)?

We currently implement a JupyterServerProvider, which allows the user to select one of our servers and triggers the kernel selector. This happens in the context of a flow where:

1. user triggers the Notebook: Select Notebook Kernel Command
2. user picks Select Another Kernel...
3. user picks our JupyterServerCollection
4. user selects a server and the kernel selector is triggered

Is there a way we could trigger step 4 for a specific server programmatically?

for context: our use case would be to surface an Add Server command where, after the server is created, it's used to trigger the kernel selector

[DonJayamanne]

@amtoney524

our use case would be to surface an Add Server command where, after the server is created, it's used to trigger the kernel selector

So the Add Server command is something that will be in the command palette, is that right?
Curious, why would the user not start with the Kernel Picker first (add command and then select kernel, all in 1 step),
instead of opening a notebook and then selecting a comment

Is this an extension I can try out?

[amtoney524]

@DonJayamanne thanks so much for your reply! there's not an extension that can be tried out yet but the dedicated command would be mainly for convenience (e.g., a shortcut to bypass steps 1 -3 in the example above).

on a related note, if the user has the ability to delete a kernel, how do we ensure the kernel selector gets updated?

it looks like the kernel selector will default to another kernel in its place; however, running a cell does not seem to work.