bdwyertech about puppet-vmwaretools

[luke-vidler]

Nice - saves me from explaining to the systems guys the vmwaretools = 'unmanaged'

[razorsedge]

Is there any documentation on why VMware ships this setting as false?

[bdwyertech]

As far as I know, this setting is set to true when the VMware Tools are
installed via any method other than installing using the VMware Tools
Installer ISO (right click VM, install VMware Tools). I think it is to
prevent someone from upgrading the VMware Tools manually outside of package
management. However, I have not found this to be an issue; I just wouldn't
enable auto-upgrade VMware Tools to keep package management in sync. When
I see an out of date on vCenter, I run a yum update vmware* instead. As
far as documentation goes, I am not sure! I have found documentation on
the VMware Tools to be rather lacking when it comes to things like that. I
think I initially found out about that setting via a blog!

On Fri, Dec 7, 2012 at 11:59 PM, Mike Arnold [email protected]:

Is there any documentation on why VMware ships this setting as false?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-11155037.

[razorsedge]

f13a05f has support for this option. I should be able to get a release out in the next week or so.

[bdwyertech]

Awesome! Glad you were able to incorporate that, I think many will find it
useful.
On Dec 13, 2012 1:33 AM, "Mike Arnold" [email protected] wrote:

f13a05f f13a05fhas support for this option. I should be able to get a release out in the
next week or so.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-11324018.

[razorsedge]

Version 4.2.0 released with this fix.