DVT connection configurations are file based and require multiple secret manager entries to keep them secure

Hi,

DVT's usage of secret manager poses two issues:

1. DVT stores connection configurations in a file. This means that when we create a container image, we need to bake in the connections into the image.
2. DVT stores the secret manager information and the name of the secrets in the connections configuration. Each configuration parameter (host, port, username, password) has to be its own secret. This is difficult to use.

A better approach would be to store the entire connection configuration as a JSON object in the secret manager. Every command that uses a connection will need to be updated to provide an option to access the connection configuration from the secret manager rather than the filesystem.

Sundar Mudupalli