{"action":"created","issue":{"url":"https://api.github.com/repos/saltstack/salt/issues/33472","repository_url":"https://api.github.com/repos/saltstack/salt","labels_url":"https://api.github.com/repos/saltstack/salt/issues/33472/labels{/name}","comments_url":"https://api.github.com/repos/saltstack/salt/issues/33472/comments","events_url":"https://api.github.com/repos/saltstack/salt/issues/33472/events","html_url":"https://github.com/saltstack/salt/issues/33472","id":156518652,"number":33472,"title":"Running salt-ssh as non-root user on the master","user":{"login":"guettli","id":414336,"avatar_url":"https://avatars.githubusercontent.com/u/414336?v=3","gravatar_id":"","url":"https://api.github.com/users/guettli","html_url":"https://github.com/guettli","followers_url":"https://api.github.com/users/guettli/followers","following_url":"https://api.github.com/users/guettli/following{/other_user}","gists_url":"https://api.github.com/users/guettli/gists{/gist_id}","starred_url":"https://api.github.com/users/guettli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/guettli/subscriptions","organizations_url":"https://api.github.com/users/guettli/orgs","repos_url":"https://api.github.com/users/guettli/repos","events_url":"https://api.github.com/users/guettli/events{/privacy}","received_events_url":"https://api.github.com/users/guettli/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-05-24T14:12:55Z","updated_at":"2016-05-24T16:31:50Z","closed_at":null,"body":"### Description of Issue/Question\r\n\r\nI am unhappy with the current state of running salt as non-root user.\r\n\r\nQuoting: https://docs.saltstack.com/en/latest/ref/configuration/nonroot.html\r\n\r\n> In order to allow Salt to successfully run as a non-root user, ownership, and permissions need to be set such that the desired user can read from and write to the following directories (and their subdirectories, where applicable):\r\n>     /etc/salt\r\n> ...\r\n\r\n### Setup\r\n\r\nI use branch \"develop\"\r\n### Idea\r\n\r\nMost people use virtualenv for development.\r\n\r\nMy proposal: Salt searches `$VIRTUAL_ENV/etc/salt` first, if this does not exist, then it tries `/etc/salt`. Same for the other files and directories.\r\n\r\nI think this is the most easiest way to solve this.\r\n\r\nIf you think there is an even more easy way, please tell me.\r\n\r\n\r\n### Problem with /etc/salt\r\n\r\nThe current approach does not allow several installations to be on one host. \r\n\r\nI would like to have two virtualenvs: one for branch develop and one for the last stable release.\r\n\r\n### What do you think?\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/saltstack/salt/issues/comments/221328593","html_url":"https://github.com/saltstack/salt/issues/33472#issuecomment-221328593","issue_url":"https://api.github.com/repos/saltstack/salt/issues/33472","id":221328593,"user":{"login":"cachedout","id":111616,"avatar_url":"https://avatars.githubusercontent.com/u/111616?v=3","gravatar_id":"","url":"https://api.github.com/users/cachedout","html_url":"https://github.com/cachedout","followers_url":"https://api.github.com/users/cachedout/followers","following_url":"https://api.github.com/users/cachedout/following{/other_user}","gists_url":"https://api.github.com/users/cachedout/gists{/gist_id}","starred_url":"https://api.github.com/users/cachedout/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cachedout/subscriptions","organizations_url":"https://api.github.com/users/cachedout/orgs","repos_url":"https://api.github.com/users/cachedout/repos","events_url":"https://api.github.com/users/cachedout/events{/privacy}","received_events_url":"https://api.github.com/users/cachedout/received_events","type":"User","site_admin":false},"created_at":"2016-05-24T16:31:50Z","updated_at":"2016-05-24T16:31:50Z","body":"One can pass `-c` to specify a configuration directory from the command-line. I'm not sure I like the idea of suddenly changing the search path for a config and would prefer it remain explicit. We could certainly adjust the documentation to suggest this approach, however. Thoughts?"}}
{"actor":{"display_login":"cachedout"}}