{"issue":{"state":"open","created_at":"2011-12-12T11:47:32Z","updated_at":"2011-12-12T18:41:29Z","comments":1,"user":{"gravatar_id":"68b3c1e2b3c882daab62c80db52a70ed","id":124301,"url":"https://api.github.com/users/pielgrzym","login":"pielgrzym","avatar_url":"https://secure.gravatar.com/avatar/68b3c1e2b3c882daab62c80db52a70ed?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"I'm aware that one can create a gazillion functions with @_hosts operator, but wouldn't it be better to have a *context_processor* called hosts accompanied with a global setting 'do_not_iterate_over_every_host_in_env_hosts' or 'allow_empty_hosts'? For simple fabfile this approach would save a lot of hassle and would not force to create a very granular tasks (which is a good thing for bigger fabfiles, since it forces user to write less redundant code).","assignee":null,"labels":[],"id":2522083,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":498,"title":"No context_manager to narrow down hosts","html_url":"https://github.com/fabric/fabric/issues/498","closed_at":null,"url":"https://api.github.com/repos/fabric/fabric/issues/498","milestone":null},"action":"created","comment":{"created_at":"2011-12-12T18:41:29Z","updated_at":"2011-12-12T18:41:29Z","user":{"gravatar_id":"f1acc6318028fdba9874c77bc622a2fb","id":6088,"url":"https://api.github.com/users/bitprophet","login":"bitprophet","avatar_url":"https://secure.gravatar.com/avatar/f1acc6318028fdba9874c77bc622a2fb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Have you looked at [execute](http://docs.fabfile.org/en/1.3.3/api/core/tasks.html#fabric.tasks.execute)? It provides much tighter control over how a task is invoked in most situations.\r\n\r\nIf that doesn't help you then I'd need a clearer example of what you want out of this, I don't understand your question.","id":3110364,"url":"https://api.github.com/repos/fabric/fabric/issues/comments/3110364"}}