Windows Working Group agenda - 2019

[dagwieers]

The Windows Working Group is focused on improving Ansible's management of Windows hosts. We meet every week on Tuesdays at 20:00 UTC (see ical)

More information related to the Windows Working Group is available at:
https://github.com/ansible/community/wiki/Windows

Feel free to add your questions to this ticket to be discussed during the upcoming meeting.

After being discussed, raised items are being updated, and after a month resolved items are being hidden from view (but remain accessible).

(Migrated from the previous agenda at #294)

[dagwieers]

New windows modules waiting for review/feedback:

• win_format: Add win_format ansible#53925 new in v2.8
• win_optional_feature: Windows module: win_optional_feature for Windows workstations ansible#53709 new in v2.8
• win_blockinfile: Add win_blockinfile module ansible#52586
• win_domain_group_membership: Win domain group membership module ansible#52556 new in v2.8
• win_package_msp: Added new win_package_msp module. ansible#52211 merged with win_package
• win_dns_record: win_dns_record ansible#51925 WIP: win_dns_record + patches ansible#52317 new in v2.8
• win_user_profile: win_user_profile - new module ansible#50637 new in v2.8
• win_ps_module: Extend win_psmodule - the second attempt, the previous was #46516 ansible#50621 new in v2.8
• win_hyperv_guest: win_hyperv_guest: New Windows Hyper-V module ansible#50417
• win_git: Add the win_git module ansible#49524 denied
• win_credential_manager: win_credential: new module to manage credentials ansible#48840 new in v2.8
• win_psrepository: Add win_psrepository ansible#48828 new in v2.8
• win_hosts: Add new windows module: win_hosts ansible#46450 new in v2.8
• win_partition: Add win_partition ansible#46292 new in v2.8
• win_iis_webhandler: Add win_iis_webhandler ansible#45998 denied
• win_snmp: win_snmp: Initial commit ansible#45710 new in v2.8
• win_iis_logs: Add win iis logs ansible#45521 denied
• win_chocolatey_pin: win_chocolatey_pin: pin a chocolatey package ansible#44766 merged with win_chocolatey
• win_rds_cap: Add modules to manage Remote Desktop Services ansible#43406 new in v2.8
• win_rds_rap: Add modules to manage Remote Desktop Services ansible#43406 new in v2.8
• win_rds_settings: Add modules to manage Remote Desktop Services ansible#43406 new in v2.8
• win_dns_a: Adding module win_dns_a ansible#36493 implemented as win_dns_record
• win_disk_management: Adding new Windows module win_disk_management ansible#27634 split up module some more
• win_http_proxy: Added win_http_proxy and win_inet_proxy ansible#54631 new in v2.8
• win_inet_proxy: Added win_http_proxy and win_inet_proxy ansible#54631 new in v2.8

Please review these tickets on a weekly basis (if there was new progress, otherwise add instructions to the owner how to continue).

[dagwieers]

I would like to discuss and speed up these read-timeout and reconnection patches to WinRM and PSRP:

• PSRP: Add read_timeout connection parameters ansible#46850 -- PSRP: Add read_timeout connection parameters
• WinRM: Add read_timeout connection parameters ansible#49701 -- WinRM: Add read_timeout connection parameters
• Overcome "Connection Refused" on some operations diyan/pywinrm#174 -- Overcome "Connection Refused" on some operations

[it-praktyk]

Please add to the list of modules to review

• win_ps_module: Extend win_psmodule - the second attempt, the previous was #46516 ansible#50621

[it-praktyk]

I would like to discuss

• The win_disk_facts doesn't return dynamic disks ansible#51032

  • does the win_ps_disk_facts should return information about disks initiated as dynamic?
  • does the win_ps_disk_facts should return information about disks those are members of storage pools members?

  IMHO, yes, for both.

• Add a missed command ansible#50781 - I think that provided PR improves the documentation

EDIT: discussed at Jan 22 meeting, dynamic disk support would be good, discussed details of linking to existing setup docs

[jborean93]

Talk about how we want to approach ansible/ansible#51063.

The decision was to make the check case insensitive but to add a warning saying this will change sometime in the future.

[jborean93]

Whether we want to support scenarios like ansible/ansible#50133. This scenario is around disabling a resource without specifying some of the mandatory options we require when creating it.

If we do then it requires a bugfix otherwise we should update the documentation. This leads into some other modules where we have been mixed in how we handle this type of scenario.

EDIT: discussed at Jan 22 meeting; in general, if an irregular state change ends up requiring creation (eg, disabled), it should be a runtime error if the resource is missing and the necessary args to create are not specified, rather than always requiring the creation args to be specified on all state changes.

[jborean93]

Talk about whether we want to include support for appx/msix in win_package or put that in it's own module ansible/ansible#50864.

The decision was to keep the PR as is and support appx/msix in win_package.

[dagwieers]

We have 14 "new" modules in the queue, some of these are in the queue for months with no activity. I think we need to bite the bullet and make a decision. Some of these modules would be better merged so they get some traction from users (as they may be too niche to expect more feedback as a PR)

Maybe it could also help us merge some modules faster if the contributor confirms he's planning to support the module actively onwards?

Update: We decided to cover these during the next Windows WG meeting on 2019-01-29.