{"action":"opened","issue":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6379","repository_url":"https://api.github.com/repos/travis-ci/travis-ci","labels_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6379/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6379/comments","events_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6379/events","html_url":"https://github.com/travis-ci/travis-ci/issues/6379","id":168319658,"number":6379,"title":"Add TLS support to the provided rabbitmq server","user":{"login":"edmorley","id":501702,"avatar_url":"https://avatars.githubusercontent.com/u/501702?v=3","gravatar_id":"","url":"https://api.github.com/users/edmorley","html_url":"https://github.com/edmorley","followers_url":"https://api.github.com/users/edmorley/followers","following_url":"https://api.github.com/users/edmorley/following{/other_user}","gists_url":"https://api.github.com/users/edmorley/gists{/gist_id}","starred_url":"https://api.github.com/users/edmorley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/edmorley/subscriptions","organizations_url":"https://api.github.com/users/edmorley/orgs","repos_url":"https://api.github.com/users/edmorley/repos","events_url":"https://api.github.com/users/edmorley/events{/privacy}","received_events_url":"https://api.github.com/users/edmorley/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-29T13:01:37Z","updated_at":"2016-07-29T13:01:37Z","closed_at":null,"body":"To improve parity between testing and production environments, it would be great if the [Travis-provided rabbitmq service](https://docs.travis-ci.com/user/database-setup/#RabbitMQ) supported TLS.\r\n\r\nThe service is provisioned here:\r\nhttps://github.com/travis-ci/travis-cookbooks/blob/master/cookbooks/travis_build_environment/recipes/rabbitmq.rb\r\n\r\nUsing the upstream rabbitmq-server cookbook:\r\nhttps://supermarket.chef.io/cookbooks/rabbitmq\r\n\r\nWhich already has SSL support:\r\nhttps://github.com/rabbitmq/rabbitmq-cookbook/blob/91c8ea61f1d58a383f118e5d2be131e56b9c2df7/attributes/default.rb#L86-L93\r\n\r\nI'm presuming the process would roughly be:\r\n1) Check whether enabling the `ssl` pref means connections to the standard non-TLS port of 5672 are still permitted\r\n2) Come up with something similar to travis-ci/travis-cookbooks#523 for creating the self-signed certs\r\n3) Ideally add these self-signed certs to the system store, so libraries that use refer to it don't have to manually define CA certs\r\n4) Add documentation for using TLS, including the paths to the certs for use with libraries where they'll need defining manually\r\n\r\nI don't believe there is a way to control whether a user must use TLS or not (unlike mysql), so I'd imagine the same `guest:guest` user would be used for TLS too.\r\n\r\nMany thanks :-)"}}
{"actor":{"display_login":"edmorley"}}