{"action":"created","issue":{"url":"https://api.github.com/repos/fugue/credstash/issues/95","repository_url":"https://api.github.com/repos/fugue/credstash","labels_url":"https://api.github.com/repos/fugue/credstash/issues/95/labels{/name}","comments_url":"https://api.github.com/repos/fugue/credstash/issues/95/comments","events_url":"https://api.github.com/repos/fugue/credstash/issues/95/events","html_url":"https://github.com/fugue/credstash/issues/95","id":173660521,"number":95,"title":"Recommended workflow in multiple environments?","user":{"login":"machira","id":3925003,"avatar_url":"https://avatars.githubusercontent.com/u/3925003?v=3","gravatar_id":"","url":"https://api.github.com/users/machira","html_url":"https://github.com/machira","followers_url":"https://api.github.com/users/machira/followers","following_url":"https://api.github.com/users/machira/following{/other_user}","gists_url":"https://api.github.com/users/machira/gists{/gist_id}","starred_url":"https://api.github.com/users/machira/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/machira/subscriptions","organizations_url":"https://api.github.com/users/machira/orgs","repos_url":"https://api.github.com/users/machira/repos","events_url":"https://api.github.com/users/machira/events{/privacy}","received_events_url":"https://api.github.com/users/machira/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-28T18:35:17Z","updated_at":"2016-09-03T09:50:03Z","closed_at":null,"body":"Hey! I would like to use credstash to store secrets in different environments (staging, qa, prod). Initially, I thought I could use the context, and credstash would handle creating the duplicate rows and retrieving the correct credential given context. But after spending a bit of time seeing how the application works, I realize that this is not correct, and setting  DBPASSWORD context=qa, then DBPASSWORD context=prod would cause a collision. \r\nThe present idea is to use different tables for each environment. This seems to be working, but I am wondering if there is a more recommended approach. \r\nThanks for this awesome utility!"},"comment":{"url":"https://api.github.com/repos/fugue/credstash/issues/comments/244537557","html_url":"https://github.com/fugue/credstash/issues/95#issuecomment-244537557","issue_url":"https://api.github.com/repos/fugue/credstash/issues/95","id":244537557,"user":{"login":"richardnbanks","id":399107,"avatar_url":"https://avatars.githubusercontent.com/u/399107?v=3","gravatar_id":"","url":"https://api.github.com/users/richardnbanks","html_url":"https://github.com/richardnbanks","followers_url":"https://api.github.com/users/richardnbanks/followers","following_url":"https://api.github.com/users/richardnbanks/following{/other_user}","gists_url":"https://api.github.com/users/richardnbanks/gists{/gist_id}","starred_url":"https://api.github.com/users/richardnbanks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/richardnbanks/subscriptions","organizations_url":"https://api.github.com/users/richardnbanks/orgs","repos_url":"https://api.github.com/users/richardnbanks/repos","events_url":"https://api.github.com/users/richardnbanks/events{/privacy}","received_events_url":"https://api.github.com/users/richardnbanks/received_events","type":"User","site_admin":false},"created_at":"2016-09-03T09:50:03Z","updated_at":"2016-09-03T09:50:03Z","body":"Hi,\r\n\r\nThe way I'm looking at solving this is through key naming. So I would get information by running one of following depending on the environment:\r\n\r\ncredstash -k DevKey get app.db.pass.dev\r\ncredstash -k QAKey get app.db.pass.qa\r\ncredstash -k ProdKey get app.db.pass.prod\r\n\r\nAs I understand it, the context is stored separately from the credential-name which must be unique."}}
{"actor":{"display_login":"richardnbanks"}}