{"action":"created","issue":{"url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver/issues/4","repository_url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver","labels_url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver/issues/4/comments","events_url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver/issues/4/events","html_url":"https://github.com/Azure/azurefile-dockervolumedriver/issues/4","id":120592271,"number":4,"title":"Support multiple storage accounts","user":{"login":"pksorensen","id":2718591,"avatar_url":"https://avatars.githubusercontent.com/u/2718591?v=3","gravatar_id":"","url":"https://api.github.com/users/pksorensen","html_url":"https://github.com/pksorensen","followers_url":"https://api.github.com/users/pksorensen/followers","following_url":"https://api.github.com/users/pksorensen/following{/other_user}","gists_url":"https://api.github.com/users/pksorensen/gists{/gist_id}","starred_url":"https://api.github.com/users/pksorensen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pksorensen/subscriptions","organizations_url":"https://api.github.com/users/pksorensen/orgs","repos_url":"https://api.github.com/users/pksorensen/repos","events_url":"https://api.github.com/users/pksorensen/events{/privacy}","received_events_url":"https://api.github.com/users/pksorensen/received_events","type":"User","site_admin":false},"labels":[{"id":313080113,"url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver/labels/feature%20request","name":"feature request","color":"fad8c7","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2015-12-05T22:25:46Z","updated_at":"2016-11-22T16:18:39Z","closed_at":null,"body":"To support high availability and scalability it would make sense to support volumes across multiple storage accounts. \n\nOne option would be to do `-o account=accountname -o share=shareName` when creating the volume.\n\nAs of configuration for all account, secrets - it would be really nice if all secrets was coming from azure keyvault.\n\nThinking that we could give the volumedriver the clientid and clientsecret of an azure ad application identity and then whenever it needs a key for a accountName for the first time it would get a token from azure ad and then fetch it from https://myvault.vaults.azure.com/secrets/avd-accountname/\n\nPersonally I prefer to prefix secrets with the name of there purpose, in this case avd for azurevolumedriver - but it could simply be /accountname/ also.\n"},"comment":{"url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver/issues/comments/262286645","html_url":"https://github.com/Azure/azurefile-dockervolumedriver/issues/4#issuecomment-262286645","issue_url":"https://api.github.com/repos/Azure/azurefile-dockervolumedriver/issues/4","id":262286645,"user":{"login":"ahmetalpbalkan","id":159209,"avatar_url":"https://avatars.githubusercontent.com/u/159209?v=3","gravatar_id":"","url":"https://api.github.com/users/ahmetalpbalkan","html_url":"https://github.com/ahmetalpbalkan","followers_url":"https://api.github.com/users/ahmetalpbalkan/followers","following_url":"https://api.github.com/users/ahmetalpbalkan/following{/other_user}","gists_url":"https://api.github.com/users/ahmetalpbalkan/gists{/gist_id}","starred_url":"https://api.github.com/users/ahmetalpbalkan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ahmetalpbalkan/subscriptions","organizations_url":"https://api.github.com/users/ahmetalpbalkan/orgs","repos_url":"https://api.github.com/users/ahmetalpbalkan/repos","events_url":"https://api.github.com/users/ahmetalpbalkan/events{/privacy}","received_events_url":"https://api.github.com/users/ahmetalpbalkan/received_events","type":"User","site_admin":false},"created_at":"2016-11-22T16:18:39Z","updated_at":"2016-11-22T16:18:39Z","body":"@pksorensen Key Vault is capable of storing text credentials, however you can't specify them on VM model's \"secrets\" section to have them securely delivered to the instances. I said \"delivery\" in my statement earlier. I am guessing you call KV API to retrieve the secrets inside the machines. However, for cert type of secrets, you can have them delivered to the machine automatically.\r\n\r\nRegardless, this issue contains 2 issues. 1) multiple accounts 2) KV support. We should probably separate them."}}
{"actor":{"display_login":"ahmetalpbalkan"}}