{"action":"closed","issue":{"url":"https://api.github.com/repos/serverless/serverless/issues/939","repository_url":"https://api.github.com/repos/serverless/serverless","labels_url":"https://api.github.com/repos/serverless/serverless/issues/939/labels{/name}","comments_url":"https://api.github.com/repos/serverless/serverless/issues/939/comments","events_url":"https://api.github.com/repos/serverless/serverless/issues/939/events","html_url":"https://github.com/serverless/serverless/issues/939","id":145615254,"number":939,"title":"Generated Scheduled Event configuration should explicitly include `enabled: false`","user":{"login":"ianserlin","id":125881,"avatar_url":"https://avatars.githubusercontent.com/u/125881?v=3","gravatar_id":"","url":"https://api.github.com/users/ianserlin","html_url":"https://github.com/ianserlin","followers_url":"https://api.github.com/users/ianserlin/followers","following_url":"https://api.github.com/users/ianserlin/following{/other_user}","gists_url":"https://api.github.com/users/ianserlin/gists{/gist_id}","starred_url":"https://api.github.com/users/ianserlin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ianserlin/subscriptions","organizations_url":"https://api.github.com/users/ianserlin/orgs","repos_url":"https://api.github.com/users/ianserlin/repos","events_url":"https://api.github.com/users/ianserlin/events{/privacy}","received_events_url":"https://api.github.com/users/ianserlin/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-04T08:15:55Z","updated_at":"2016-05-12T12:21:12Z","closed_at":"2016-05-12T12:21:12Z","body":"v0.5.1\r\n\r\nWhen generating a new scheduled-type event, the resulting snippet added to `s-function.json` is:\r\n\r\n_Current_\r\n```\r\n  \"events\": [\r\n    {\r\n      \"name\": \"mySchedule\",\r\n      \"type\": \"schedule\",\r\n      \"config\": {\r\n        \"schedule\": \"rate(5 minutes)\"\r\n      }\r\n    }\r\n  ],\r\n```\r\n\r\n_Proposed_\r\n```\r\n  \"events\": [\r\n    {\r\n      \"name\": \"mySchedule\",\r\n      \"type\": \"schedule\",\r\n      \"config\": {\r\n        \"enabled\": false,\r\n        \"schedule\": \"rate(5 minutes)\"\r\n      }\r\n    }\r\n  ],\r\n```\r\n\r\n\r\nFor anyone not well versed in AWS (some large proportion of serverless's target userbase), it's non-obvious that the event, when deployed, will not be enabled. I believe this also does not match the deployed enabled/disabled state of other triggers like DynamoDB streams. While this flag is mentioned in the guide, adding the line `\"enabled\": false` by default will help make it easier for people to reason about what is happening when they expect to see their lamdba running/events hooked up in the AWS Console after deployment, but have not enabled the CloudWatch Event yet."}}