{"action":"opened","issue":{"url":"https://api.github.com/repos/CentOS-PaaS-SIG/linchpin/issues/299","repository_url":"https://api.github.com/repos/CentOS-PaaS-SIG/linchpin","labels_url":"https://api.github.com/repos/CentOS-PaaS-SIG/linchpin/issues/299/labels{/name}","comments_url":"https://api.github.com/repos/CentOS-PaaS-SIG/linchpin/issues/299/comments","events_url":"https://api.github.com/repos/CentOS-PaaS-SIG/linchpin/issues/299/events","html_url":"https://github.com/CentOS-PaaS-SIG/linchpin/issues/299","id":239520737,"number":299,"title":"Search workspace/credentials for creds, or allow workspace/credentials to be defined in workspace/linchpin.conf","user":{"login":"robled","id":3211560,"avatar_url":"https://avatars3.githubusercontent.com/u/3211560?v=3","gravatar_id":"","url":"https://api.github.com/users/robled","html_url":"https://github.com/robled","followers_url":"https://api.github.com/users/robled/followers","following_url":"https://api.github.com/users/robled/following{/other_user}","gists_url":"https://api.github.com/users/robled/gists{/gist_id}","starred_url":"https://api.github.com/users/robled/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robled/subscriptions","organizations_url":"https://api.github.com/users/robled/orgs","repos_url":"https://api.github.com/users/robled/repos","events_url":"https://api.github.com/users/robled/events{/privacy}","received_events_url":"https://api.github.com/users/robled/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-06-29T15:34:32Z","updated_at":"2017-06-29T15:34:32Z","closed_at":null,"body":"In CI, it's common to store the full stack of things needed to make provisioning happen in source control, including credentials (properly secured, of course).  As such, looking for credentials outside of the linchpin workspace is less than desirable for CI, as when starting a build you would commonly check out *everything* needed to provision for that build from source control, and paths like **$HOME/.config** are not useful for this case.   \r\n\r\nThis improvement would help to serve a higher-level purpose, where if you point linchpin at a workspace checked out from source control, then from there it can find *everything* it needs to make things go, including **linchpin.conf** (there's already another ticket for finding this file in the linchpin workspace), as well as credentials."}}
{"actor":{"display_login":"robled"}}