{"action":"created","issue":{"url":"https://api.github.com/repos/kapost/circuitry/issues/19","labels_url":"https://api.github.com/repos/kapost/circuitry/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/kapost/circuitry/issues/19/comments","events_url":"https://api.github.com/repos/kapost/circuitry/issues/19/events","html_url":"https://github.com/kapost/circuitry/pull/19","id":98633208,"number":19,"title":"[WIP] First pass at automated provisioning","user":{"login":"mhuggins","id":169093,"avatar_url":"https://avatars.githubusercontent.com/u/169093?v=3","gravatar_id":"","url":"https://api.github.com/users/mhuggins","html_url":"https://github.com/mhuggins","followers_url":"https://api.github.com/users/mhuggins/followers","following_url":"https://api.github.com/users/mhuggins/following{/other_user}","gists_url":"https://api.github.com/users/mhuggins/gists{/gist_id}","starred_url":"https://api.github.com/users/mhuggins/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mhuggins/subscriptions","organizations_url":"https://api.github.com/users/mhuggins/orgs","repos_url":"https://api.github.com/users/mhuggins/repos","events_url":"https://api.github.com/users/mhuggins/events{/privacy}","received_events_url":"https://api.github.com/users/mhuggins/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-02T20:02:46Z","updated_at":"2015-08-10T17:49:17Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/kapost/circuitry/pulls/19","html_url":"https://github.com/kapost/circuitry/pull/19","diff_url":"https://github.com/kapost/circuitry/pull/19.diff","patch_url":"https://github.com/kapost/circuitry/pull/19.patch"},"body":"@kapost/core Took a stab at provisioning topics, queues, and subscriptions.  There are still a number of considerations not included here, such as:\r\n\r\n* ~~Failure queues (dead letter)~~\r\n  * ~~Creation~~\r\n  * ~~Association with subscribed queues~~\r\n* [Queue options](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_CreateQueue.html#API_CreateQueue_RequestParameters):\r\n  * DelaySeconds\r\n  * MaximumMessageSize\r\n  * MessageRetentionPeriod\r\n  * ~~Policy~~\r\n  * ReceiveMessageWaitTimeSeconds\r\n  * VisibilityTimeout\r\n* ~~AWS accounts: currently uses the circuitry configuration and assumes that the same user privileged for writing to SNS & reading from SQS also has rights to create SNS topics, SNS subscriptions, and SQS queues.~~\r\n* Bonus: no tests yet."},"comment":{"url":"https://api.github.com/repos/kapost/circuitry/issues/comments/129546963","html_url":"https://github.com/kapost/circuitry/pull/19#issuecomment-129546963","issue_url":"https://api.github.com/repos/kapost/circuitry/issues/19","id":129546963,"user":{"login":"brandonc","id":174332,"avatar_url":"https://avatars.githubusercontent.com/u/174332?v=3","gravatar_id":"","url":"https://api.github.com/users/brandonc","html_url":"https://github.com/brandonc","followers_url":"https://api.github.com/users/brandonc/followers","following_url":"https://api.github.com/users/brandonc/following{/other_user}","gists_url":"https://api.github.com/users/brandonc/gists{/gist_id}","starred_url":"https://api.github.com/users/brandonc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brandonc/subscriptions","organizations_url":"https://api.github.com/users/brandonc/orgs","repos_url":"https://api.github.com/users/brandonc/repos","events_url":"https://api.github.com/users/brandonc/events{/privacy}","received_events_url":"https://api.github.com/users/brandonc/received_events","type":"User","site_admin":false},"created_at":"2015-08-10T17:49:17Z","updated_at":"2015-08-10T17:49:17Z","body":"I think the CLI approach is useful but its scope is limited by circuitry\r\n\r\nI am thinking this might be the job for a separate gem that provides a [HerokuSan deployment strategy](http://pivotallabs.com/deploy-strategies-for-herokusan/) which automatically provisions any AWS resource according to a config\r\n\r\nWith each deploy, it would ensure that all the resources are created, and the catalog of dependencies could all be nicely recorded in a yml file.\r\n\r\n"}}