{"action":"closed","issue":{"url":"https://api.github.com/repos/openbridge/ob_bulkstash/issues/3","repository_url":"https://api.github.com/repos/openbridge/ob_bulkstash","labels_url":"https://api.github.com/repos/openbridge/ob_bulkstash/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/openbridge/ob_bulkstash/issues/3/comments","events_url":"https://api.github.com/repos/openbridge/ob_bulkstash/issues/3/events","html_url":"https://github.com/openbridge/ob_bulkstash/issues/3","id":309254120,"number":3,"title":"Support for Secrets","user":{"login":"efrecon","id":9443924,"avatar_url":"https://avatars3.githubusercontent.com/u/9443924?v=4","gravatar_id":"","url":"https://api.github.com/users/efrecon","html_url":"https://github.com/efrecon","followers_url":"https://api.github.com/users/efrecon/followers","following_url":"https://api.github.com/users/efrecon/following{/other_user}","gists_url":"https://api.github.com/users/efrecon/gists{/gist_id}","starred_url":"https://api.github.com/users/efrecon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/efrecon/subscriptions","organizations_url":"https://api.github.com/users/efrecon/orgs","repos_url":"https://api.github.com/users/efrecon/repos","events_url":"https://api.github.com/users/efrecon/events{/privacy}","received_events_url":"https://api.github.com/users/efrecon/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-03-28T07:41:41Z","updated_at":"2018-03-28T15:47:06Z","closed_at":"2018-03-28T15:47:06Z","author_association":"CONTRIBUTOR","body":"According to the [doc](https://docs.docker.com/engine/swarm/secrets/)\r\n\r\n> you can use Docker secrets to centrally manage this data and securely transmit it to only those containers that need access to it. Secrets are encrypted during transit and at rest in a Docker swarm. A given secret is only accessible to those services which have been granted explicit access to it, and only while those service tasks are running.\r\n\r\nPR #2 provides support for carrying secretive information such as tokens or passwords for the sources and destinations using secrets. This follows the idea of the image itself, an image with a strong focus on configuration through environment variables (and not a configuration file, even if this is still possible). The PR achieves this through looking into the content of environment variables and resolving those that follow a given template to the file that it points at. This is slightly different from the \"regular\" Docker way. Official images use `_FILE` at the end of environment variables to take information from a file instead. However, as the variables are read by `rclone`, the mechanism in the PR provides a solution that does not imply any modification of the `rclone` binary implementation, thus will be able to work in future version of rclone.\r\n\r\nWould you mind considering taking in the PR?"}}
{"actor":{"display_login":"tspicer"}}