[chef] RE: install & upgrading windows package with version in name

["Smith, Scott" < >]

Hi Grzegorz,

 

I’ve encountered this issue myself and my solution was to use a second resource. Change your original windows_package’s action to :remove and create a new resource for the new package. Once you’re absolutely sure the first package doesn’t exist in your infrastructure, you can remove the original resource. It works, but I’m not thrilled with the solution. Here’s hoping someone else in the community has some magic to share.

 

Thanks,

 

Scott

 

From: Grzegorz Marszałek [mailto:
Sent: Monday, September 28, 2015 1:18 PM
To:
Subject: [chef] install & upgrading windows package with version in name

 

Hello!

 

I use chef to manage windows machines - and I install a lot of windows packages. Some of them have bad habit to include version in package name. This is bad when you want to do application upgrades, or may be application upgrades them selves.

 

So - how do you manage installing & upgrading windows apps with version in package name (that is: when you click on installed programs you see app name with version on the list)?

 

Bye

--

Grzegorz Marszałek

---

Join us for Xactware User Conference 2016 on Feb. 9-10 in Salt Lake City. Stay February 11 for an extra day of free training. Visit xactwareuserconference.com for more information.

---

This email is intended solely for the recipient. It may contain privileged, proprietary or confidential information or material. If you are not the intended recipient, please delete this email and any attachments and notify the sender of the error.