|
| 1 | +#Windows Working Group Meeting |
| 2 | +#Notes from 2025-07-17 |
| 3 | + |
| 4 | +##Attendees |
| 5 | +- Shane Lee (@twangboy) |
| 6 | +- Dafyddj |
| 7 | + |
| 8 | +##Agenda |
| 9 | +- Welcome |
| 10 | +- CICD Status |
| 11 | +- 3006.x failing |
| 12 | +- 3007.x failing |
| 13 | +- master failing |
| 14 | + |
| 15 | +- Releases: |
| 16 | +- 3006.13 : released |
| 17 | +- 3007.5 : released |
| 18 | +- 3006.14 : released |
| 19 | +- 3007.6 : released |
| 20 | +- 3008rc : fall 2025 |
| 21 | + |
| 22 | +- Discussed Previously: |
| 23 | +- Tenable Scans causing DoS on master |
| 24 | +https://github.com/saltstack/salt/pull/66519 (issue) |
| 25 | + FIXED |
| 26 | +- Community maintainers need clear guidance on what we want them to do. If |
| 27 | + the maintainer has an hour to give to Salt, what should they do? We need a |
| 28 | + policy document with clear guidance. |
| 29 | + |
| 30 | +- Noteable PRs: |
| 31 | +- cmdmod -https://github.com/saltstack/salt/pull/68156 |
| 32 | +- runas -https://github.com/saltstack/salt/pull/68157 |
| 33 | + |
| 34 | +- Community Issues and Discussion |
| 35 | +- Working on the pkg.installed with force option |
| 36 | +- Master changes IP Address |
| 37 | +- The minions lose connectivity when the master IP address changes |
| 38 | +- This happens on minions (laptops) that go into hybernation |
| 39 | +- Restarting the minion service allows the minion to reconnect |
| 40 | +- Why does the service need to be restarted |
| 41 | +- Winrepo is looking good |
| 42 | +- Maybe need to trim the repo down |
| 43 | +- Use SPM (Salt Package Manager) to reduce reliance on GitFS |
| 44 | +- Maybe have a contrib repo for all the old packages |
| 45 | +- Discussed using the`winrepo_branch` config option on the master to set |
| 46 | + the tag for winrepo. That way the users aren't getting every little thing |
| 47 | + that is happening on the master branch. They could also avoid getting a |
| 48 | + breaking change when we start removing package defintions because they're |
| 49 | + pinned to a specific version. |
| 50 | +- We need to create a new repo`salt-winrepo-contrib` as a holder for |
| 51 | + deprecated package definitions |
| 52 | +- We need to provide documentation on how to pin winrepo to a specific |
| 53 | + release. |
| 54 | +- Message that we're doing this to prevent unexpected changes from impacting |
| 55 | + them. Keep an eye on release notes. |
| 56 | + |
| 57 | +##TODO |
| 58 | +- Twangboy: Investigate the pkg.install 3006.10 issue |
| 59 | +https://github.com/saltstack/salt/issues/67902 |
| 60 | +- Twangboy: Any idea when the next 3006.11 will happen |
| 61 | +- Twangboy: Investigate making powershell the default shell on Windows |
| 62 | +- Twangboy: We need to communicate better with our community volunteers exactly |
| 63 | + what we want them to do... how they can contribute. |
| 64 | +- Twangboy: |
| 65 | +- Community maintainers need clear guidance on what we want them to do. If |
| 66 | + the maintainer has an hour to give to Salt, what should they do? We need a |
| 67 | + policy document with clear guidance. |
| 68 | +- Twangboy: |
| 69 | +- lgpo_reg: |
| 70 | +- Currently writes the registry as well, maybe we need to make that |
| 71 | + configurable |
| 72 | +- User policies are set in the context of the service account. They probably |
| 73 | + shouldn't be written to the registry at all as that is applied when the |
| 74 | + user logs in. |
| 75 | +- Need to create a module that will generate a state based on the contents |
| 76 | + of the Registry.pol file. This could/should be a salt extension |
| 77 | +- Dafydd: Investigate pythonnet |
| 78 | +https://devblogs.microsoft.com/powershell/hosting-powershell-in-a-python-script/ |
| 79 | +- Dafydd: Create an issue for the lgpo_reg module to not write user policies |
| 80 | + to the registry as those should be handled by Windows when the user |
| 81 | + logs in |
| 82 | + |