Skip to content
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

Support for Azure Key Vault as Shard Map Manager #157

Open
tomkerkhove opened this issue Aug 26, 2017 · 4 comments
Open

Support for Azure Key Vault as Shard Map Manager #157

tomkerkhove opened this issue Aug 26, 2017 · 4 comments
Assignees

Comments

@tomkerkhove
Copy link
Member

Are there plans to support Azure Key Vault as a Shard Map Manager?

This would allow to get rid of the database and securely store the connection strings to the shard.

@jaredmoo
Copy link
Contributor

No plans for that. Could you elaborate a bit on how shard mappings would be stored in azure key vault?

@tomkerkhove
Copy link
Member Author

Fair warning - I have no experience with using the library but this is mainly because we are now using Azure Key Vault to store the connection strings to our shards.

We basically go fetch the connection string in Azure Key Vault based on the shard key we use in the application. By doing this we can securely store the connection string and don't need a full blown DB to achieve this.

@jaredmoo
Copy link
Contributor

I see. Storing the connection string in AKV is an interesting idea. I presume it would only support ListShardMap and point mappings and the key id would have to be based on the shard key.

@tomkerkhove
Copy link
Member Author

Hm interesting, I'm not an expert with the library but is there a reason why I couldn't fully use Key Vault for everything?

@stuartpa stuartpa self-assigned this Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants