It's on the way to being deprecated (most likely we'll do it for real in 2.4)- win_package is the recommended replacement, but we've been holding off on "really" deprecating win_msi until we make some usability changes to win_package. The big one is that you have to look up the product ID to supply it to win_package, but that's not necessary with an MSI unless it's being hosted remotely (so the module can query for the product_id without downloading the msi). So we'll be relaxing that requirement, as well as tweaking around a few other things.
On Wednesday, April 19, 2017 at 12:25:51 PM UTC-7, Tai Kedzierski wrote: > > Hello > > *(Apologies if this is a double-post - I am sure I posted yesterday, but I > do not see the item in the list or in my activities....)* > > The docs page for the win_msi module states that the module is deprecated, > and its information seems clipped (incomplete sentence in the explanation) > > http://docs.ansible.com/ansible/win_msi_module.html > > But the general modules list does not (no "D:" on the module name) > > http://docs.ansible.com/ansible/list_of_windows_modules.html > > My questions are: > > > - Is win_msi really deprecated ? > - If so, what's the new preferred method ? > > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/3d577f27-c13e-4f39-bb68-8e447313be6a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
