winget-pkgs VS ansible.windows

7.0 is now available: https://github.com/microsoft/winget-pkgs/pull/147886

I researched this for a WinGet thing: https://github.com/microsoft/winget-pkgs/pull/110618

Ah, reminds me of that time I requested a .editorconfig file in a Microsoft repo: https://github.com/microsoft/winget-pkgs/issues/329

Take dropbox as an example. This is what the yaml manifest looks like for that if you install it through winget. It literally has a hardcoded link to an .exe installer hosted by dropbox and then just set the flags to silent. I am not spreading misinformation, you are.

It's not quite the same though, as there are different considerations when using a repository of things a unified group has decided should be included and built (or slightly modified existing) packages for and a repo where anyone can submit a package that will go through some level of vetting. In the end I still believe most this discussion is really about individuals and how much trust they apply towards different groups and sources and is not really about Linux or Windows in particular as much.

1: https://github.com/microsoft/winget-pkgs

I never used winget, but probably: - https://github.com/microsoft/winget-pkgs/issues/107858 - https://github.com/Genymobile/scrcpy/issues/4027

It's probably not on the Store, winget pulls from both the Store and a community collection of manifests on GitHub: https://github.com/microsoft/winget-pkgs

I think that's part of the problem, if you don't have that package manager to bootstrap your signature key ring, DNS is your next best bootstrap. It is, of course, a terrible bootstrap for trust, but it is one so many users on Windows have been relying on for such a long time.

For power users on any modern Windows 10/Windows 11 there is at least WinGet now. Its manifests repo is becoming a very interesting (open) source of truth for common Windows applications. Admittedly, it in most cases doesn't seem to be checking specific code signatures in most cases either, but at least includes SHA checksums.

For instance, 7zip's manifests: https://github.com/microsoft/winget-pkgs/tree/master/manifes...

It's too bad there's still not a great option for "average user that doesn't know/trust how to use a CLI", given how sadly polluted the Microsoft Store can be for many common, especially Open Source, applications. For direct instance, because winget kindly includes Microsoft Store results when searching, there is a "7zip 22" in the Microsoft Store that costs some amount of money (winget details say "PaidUnknownPrice" for the pricing information; I'm on a corporate machine right now with the actual Store access locked so can't search in the actual Store right now) and the Publisher is listed as RepackagerExpress.com. (That website currently doesn't go anywhere, giving it a spot check.)

Having seen this, I may boot up my personal machine and try to report this specific Store listing for violating the Store's Open Source policies, though I'm unsure if such whackamole is all that useful. (Seems like it might be a useful winget feature request for it to provide Store Report URLs.)

For example, see that Firefox has /S here.

collections: # see https://galaxy.ansible.com/ansible/windows - name: ansible.windows version: 2.2.0 # see https://galaxy.ansible.com/community/general - name: community.general version: 8.1.0

For example the ansible.windows collections has a plugin_utils/_quote.py file https://github.com/ansible-collections/ansible.windows/blob/main/plugins/plugin_utils/_quote.py. It's then imported by some filter plugins with https://github.com/ansible-collections/ansible.windows/blob/5b044e12c93f57a26563264690c633aef97036d6/plugins/filter/quote.py#L11-L15

I'm no expert here, but maybe you're better off using the ansible windows collection instead of just invoking Powershell, as you'll get to rely on all the functionality Ansible provides like checking the outcome, changes, handling errors, providing consistent feedback, etc., instead of being responsible for that yourself. Like, actually use it for more than firing off scripts remotely

I've tried the workarounds provided here but I haven't had any success. I'm persisting with this approach rather than the more tedious copying the script to the server, executing, and then cleaning up etc. as Ansible does the house keeping for me this way. 😅

If you do find any issues we certainly would like to hear about it and try and fix the problem if we can. You can submit an issue with the details at https://github.com/ansible-collections/ansible.windows.

It is but Parse-Args are part of the legacy module utils. Have a look at win_environment for a decent module example. It uses the newer AnsibleModule style that is good to use today. You can ignore the AddType module util if you don’t need that functionality (it doesn’t look like you do).

Here is something that might get you moving In the right direction, its a script to pull and modify the ACL's from ansiblehttps://github.com/ansible-collections/ansible.windows/blob/main/plugins/modules/win_acl.ps1

Which version of Ansible? See https://github.com/ansible-collections/ansible.windows/issues/138. This may or may not be your issue.

Just opened https://github.com/ansible-collections/ansible.windows/pull/320 which should solve this problem for you. If you do get a chance it would be great if you could test it out in your environment to see if it solves it for you.

The issue you are coming across is https://github.com/ansible-collections/ansible.windows/issues/29 which has been fixed in the ansible.windows collection. The fix was very intrusive as it required a massive rewrite in how the module gathered facts, essentially stopped using WMI/CIM. I believe these changes are present in Ansible 2.10.+ but not Ansible 2.9.. The issue here is that WMI/CIM does not allow you to get instances unless you are either an Administrator or are running an Interactive logon. For WinRM users are no longer running an interactive logon so the old code only worked for Administrators.