{"action":"created","issue":{"url":"https://api.github.com/repos/chef/chef-provisioning-azure/issues/43","repository_url":"https://api.github.com/repos/chef/chef-provisioning-azure","labels_url":"https://api.github.com/repos/chef/chef-provisioning-azure/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/chef/chef-provisioning-azure/issues/43/comments","events_url":"https://api.github.com/repos/chef/chef-provisioning-azure/issues/43/events","html_url":"https://github.com/chef/chef-provisioning-azure/issues/43","id":113739785,"number":43,"title":"machine resource :converge_only implementation?","user":{"login":"anthonyvdis","id":15354939,"avatar_url":"https://avatars.githubusercontent.com/u/15354939?v=3","gravatar_id":"","url":"https://api.github.com/users/anthonyvdis","html_url":"https://github.com/anthonyvdis","followers_url":"https://api.github.com/users/anthonyvdis/followers","following_url":"https://api.github.com/users/anthonyvdis/following{/other_user}","gists_url":"https://api.github.com/users/anthonyvdis/gists{/gist_id}","starred_url":"https://api.github.com/users/anthonyvdis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anthonyvdis/subscriptions","organizations_url":"https://api.github.com/users/anthonyvdis/orgs","repos_url":"https://api.github.com/users/anthonyvdis/repos","events_url":"https://api.github.com/users/anthonyvdis/events{/privacy}","received_events_url":"https://api.github.com/users/anthonyvdis/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-28T04:08:06Z","updated_at":"2016-02-26T21:04:25Z","closed_at":"2016-02-26T21:04:25Z","body":"It looks like the :converge_only action isn't implemented because the connect_to_machine method isn't implemented in the driver. I would like to have this action because I am calling the machine resource multiple times on the same VM, and each run appears to re-download and re-run the chef-client omnibus installer, which is adding unnecessary time to my provisioning process.\r\n\r\nAttempting the action gives this error:\r\n\r\n    Chef::Provisioning::AzureDriver::Driver does not implement connect_to_machine\r\n\r\nI see this issue: https://github.com/chef/chef-provisioning-azure/issues/21 but I'm not sure how related it is.\r\n\r\nCan anyone advise on implementing connect_to_machine? Is it planned? Possible? Can we instead simply prevent the default action from reinstalling the chef-client if it's already there?\r\n\r\nThanks"},"comment":{"url":"https://api.github.com/repos/chef/chef-provisioning-azure/issues/comments/189483012","html_url":"https://github.com/chef/chef-provisioning-azure/issues/43#issuecomment-189483012","issue_url":"https://api.github.com/repos/chef/chef-provisioning-azure/issues/43","id":189483012,"user":{"login":"stuartpreston","id":6384654,"avatar_url":"https://avatars.githubusercontent.com/u/6384654?v=3","gravatar_id":"","url":"https://api.github.com/users/stuartpreston","html_url":"https://github.com/stuartpreston","followers_url":"https://api.github.com/users/stuartpreston/followers","following_url":"https://api.github.com/users/stuartpreston/following{/other_user}","gists_url":"https://api.github.com/users/stuartpreston/gists{/gist_id}","starred_url":"https://api.github.com/users/stuartpreston/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stuartpreston/subscriptions","organizations_url":"https://api.github.com/users/stuartpreston/orgs","repos_url":"https://api.github.com/users/stuartpreston/repos","events_url":"https://api.github.com/users/stuartpreston/events{/privacy}","received_events_url":"https://api.github.com/users/stuartpreston/received_events","type":"User","site_admin":false},"created_at":"2016-02-26T21:04:25Z","updated_at":"2016-02-26T21:04:25Z","body":"I personally haven't spent any time on this. The problem with connect_to_machine is that it relies on a direct WinRM connection from your provisioning node/client, and in Azure this is not guaranteed and/or likely to be on a different set of ports per VM.\r\n\r\nFor V2/Azure Resource Manager mode machines, it is even less likely that you would have direct connectivity to the WinRM ports on each VM, hence the preference there is to use Chef Provisioning (see http://github.com/pendrica/chef-provisioning-azurerm) as a means to get a VM or other resources created and up and running with a Chef VM Extension, which then is a bit more self managing.\r\n\r\nI'm going to close this for now but please reopen or @ me if you want to discuss further."}}