If it's an msi, the module can scan the package itself to get the 
product_id. If it's an exe then it would need the product_id or one of the 
creates_* options to try and add some idempotency.

On Friday, December 23, 2022 at 12:24:04 PM UTC+10 pyyg...@gmail.com wrote:

> Hi everyone,
>
> About win_package, in the official document, it mentions: product_id value 
> is ignored if path is set to a local accesible file path and the package is 
> not an exe.
>
> So, if I want to install MSI package, and I specify the path to a local 
> accessible file path, then I don't need to set product_id, correct ? If I 
> don't set product_id, how it can know if the package has been installed?  
> by searching for the InstallSource in registry?
>

-- 
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 ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/3791a06f-d134-4cea-80e9-2835db1b237an%40googlegroups.com.

Reply via email to