Programmatically import server list

[audetto]

Feature Request

Description of Problem:

In our organisation the password used to connect to kdb servers expires every couple of days.

We have tools to regenerate the server list (json or qpad format), but all users must manually reimport it each time with numerous clicks which after a while become very tedious.

I would like to have a way to programmatically import the new server list into kdb studio settings with minimal user interaction.

Potential Solutions:

I would like to have a command line switch to import server list which does not require any click.
Or a separate main like

kdb-studio/src/main/studio/ui/QPadImportDialog.java

Line 222 in 20616f6

public static void main(String[] args) {

to do it.

[dzmipt]

In your use-case, is it possible to centrally manager the server configuration? I have the following proposal (which requires development)...

I think it might be useful if the Studio loads the configuration from the remote location. The user only needs to register the remote location to load the configuration. Probably the server can return different configuration to different users (e.g. depending on their roles).

Here are a list of points/questions which makes sense to think about in such design

• what is the protocol between the server and kdbStudio on client machines? Probably it can be REST or an ipc call to a kdb instance...
• Does it poll (the client periodically refreshes the list) or server pushes updates? Likely the poll is better. In this case, how often it happens? May be the user can reload from his UI.
• What happens if the user has an open tab with a server which disappeared in the configuration from the remote server
• May be we need to support several (not a single) remote server and merge the configurations. And in addition, the user can manual add his/her own connections
• What should be the behaviour in case server names in remote configs clashes with user defined connections ?

[audetto]

That would be the ultimate integration.
What worries me is that it might become a project across N teams and eventually going nowhere. And servers configuration is not so stable that can be managed centrally.

One thing I did not mention is that passwords are user-specific and there is a fully automated way for a user logged in a machine to retrieve her own password (or token if you prefer) programmatically.

If I may, I could turn your proposal upside down:

I can see in the qpad import dialog that there is a drop down "authentication method". What if I could write my own java plugin and enter a class name? implementing a get_credentials_for(server, port) method.

If this were called on each startup (or each server change), I think it could work.