{"action":"created","issue":{"url":"https://api.github.com/repos/Azure/Azure-Functions/issues/75","repository_url":"https://api.github.com/repos/Azure/Azure-Functions","labels_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/75/labels{/name}","comments_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/75/comments","events_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/75/events","html_url":"https://github.com/Azure/Azure-Functions/issues/75","id":190802593,"number":75,"title":"Allow running a Function for more than 5 minutes on a Consumption plan","user":{"login":"lindydonna","id":4260261,"avatar_url":"https://avatars.githubusercontent.com/u/4260261?v=3","gravatar_id":"","url":"https://api.github.com/users/lindydonna","html_url":"https://github.com/lindydonna","followers_url":"https://api.github.com/users/lindydonna/followers","following_url":"https://api.github.com/users/lindydonna/following{/other_user}","gists_url":"https://api.github.com/users/lindydonna/gists{/gist_id}","starred_url":"https://api.github.com/users/lindydonna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lindydonna/subscriptions","organizations_url":"https://api.github.com/users/lindydonna/orgs","repos_url":"https://api.github.com/users/lindydonna/repos","events_url":"https://api.github.com/users/lindydonna/events{/privacy}","received_events_url":"https://api.github.com/users/lindydonna/received_events","type":"User","site_admin":false},"labels":[{"id":455906766,"url":"https://api.github.com/repos/Azure/Azure-Functions/labels/feature","name":"feature","color":"0052cc","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-11-21T18:45:21Z","updated_at":"2016-11-27T23:52:45Z","closed_at":null,"body":"Copied from: https://github.com/Azure/azure-webjobs-sdk-script/issues/18\r\n\r\nThe underlying compute platform for Consumption plan Functions does not allow running for more than 5 minutes, so the Functions host enforces this limit. There's customer feedback that it would be useful to increase this timeout.\r\n\r\nThis issue tracks work that will have to be done across the compute platform, the Functions host, and (possibly) the portal."},"comment":{"url":"https://api.github.com/repos/Azure/Azure-Functions/issues/comments/263157258","html_url":"https://github.com/Azure/Azure-Functions/issues/75#issuecomment-263157258","issue_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/75","id":263157258,"user":{"login":"mikezks","id":23002661,"avatar_url":"https://avatars.githubusercontent.com/u/23002661?v=3","gravatar_id":"","url":"https://api.github.com/users/mikezks","html_url":"https://github.com/mikezks","followers_url":"https://api.github.com/users/mikezks/followers","following_url":"https://api.github.com/users/mikezks/following{/other_user}","gists_url":"https://api.github.com/users/mikezks/gists{/gist_id}","starred_url":"https://api.github.com/users/mikezks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikezks/subscriptions","organizations_url":"https://api.github.com/users/mikezks/orgs","repos_url":"https://api.github.com/users/mikezks/repos","events_url":"https://api.github.com/users/mikezks/events{/privacy}","received_events_url":"https://api.github.com/users/mikezks/received_events","type":"User","site_admin":false},"created_at":"2016-11-27T23:52:45Z","updated_at":"2016-11-27T23:52:45Z","body":"I agree with the initial SO post: Serverless means for me, that I do not have to take care about instances, sizing up resp. down and have a clear pricing model to calculate the costs for running a job - no matter if it needs 10 sec or 5 days.\r\n\r\nIt would be good to have the choice of setting a timeout, be informed about the costs per email periodically after each definable interval, etc.\r\n\r\nBut using ARM to activate and deactivate a Function App within a Web App does not follow the principles of a serverless environment. I use these kind of services because I am convinced that Microsoft can do a better job concerning operation than I do myself. This ARM approach sounds like a workaround but not like a solution."}}
{"actor":{"display_login":"mikezks"}}