January 19th Community Call

[StevenBucher98]

Agenda -

• 2023 Team investments blog post @SteveL-MSFT
• Triple slash comments @SteveL-MSFT @sdwheeler
• PowerShell Gallery update - @adityapatwardhan
• PowerShellGet Update - @alerickson
• OpenSSH Release - @tgauth
• CloudShell Predictors - Damien
• VS Code January Stable Release - @andschwa
• PowerShell and DSC for WinGet - Demetrius
• Discussions, backporting, graph v2
• Demos

[SteveL-MSFT]

Adam Driscoll to demo psedit

[SteveL-MSFT]

Doug Finke to demo GPT + PowerShell

[kilasuit]

Discussion on December being a community run call each year going forward, as opposed to the team who run the call all the rest of the year.

[kilasuit]

I have a demo of a project I started that looks at code complexity scoring

[JustinGrote]

Loving all the demos submissions! Keep 'em coming!

[ajansveld]

Could someone talk about what bug fixes get backported to the 7.2 (LTS) release? How can the community help bring attention to critical bugs so they can be considered?

[JustinGrote]

Could someone talk about what bug fixes get backported to the 7.2 (LTS) release? How can the community help bring attention to critical bugs so they can be considered?

Do you have an example? I bet that would help.

[AspenForester]

How are people feeling about the announcement of the Graph v2 modules?
https://devblogs.microsoft.com/microsoft365dev/microsoft-graph-powershell-v2-is-now-in-public-preview-half-the-size-and-will-speed-up-your-automations/

[ajansveld]

Could someone talk about what bug fixes get backported to the 7.2 (LTS) release? How can the community help bring attention to critical bugs so they can be considered?

Do you have an example? I bet that would help.

Sure! PowerShell/PowerShell#13633 describes a bug that was fixed in 7.3 but can still bite people on 7.2.

[JustinGrote]

How are people feeling about the announcement of the Graph v2 modules? https://devblogs.microsoft.com/microsoft365dev/microsoft-graph-powershell-v2-is-now-in-public-preview-half-the-size-and-will-speed-up-your-automations/

I think it's the smart move, though they really should provide for the beta module a quick aliasing feature (e.g. alias Get-MgUser to Get-MgBetaUser) so you can test against the beta API without having to rewrite your script.

[bergmeister]

How are people feeling about the announcement of the Graph v2 modules? https://devblogs.microsoft.com/microsoft365dev/microsoft-graph-powershell-v2-is-now-in-public-preview-half-the-size-and-will-speed-up-your-automations/

I think it's the smart move, though they really should provide for the beta module a quick aliasing feature (e.g. alias Get-MgUser to Get-MgBetaUser) so you can test against the beta API without having to rewrite your script.

When AzureRM migrated to Az, they provided an Enable-AzureRmAlias command for that, so that would be good starting point https://learn.microsoft.com/en-us/powershell/azure/migrate-from-azurerm-to-az#option-2-use-compatibility-mode-with-enable-azurermalias

However, I am not sure that having different cmdlet names is the best technical option only for choosing between beta and RTM endpoint, it could instead be a switch parameter and I don't think there's a reason to not allow the usage of beta endpoints in RTM module versions since the user explicitly opts into it.
A PowerShell module in beta version to me is more about getting user feedback about cmdlet design (e.g. do new parameters or returned object structures make sense; hint: this is actually one of the weakest areas for most MG cmdlets IMHO where most users would welcome improvements) and not about whether it calls a Beta endpoint. Of course a Beta module can serve as a release train to bring brand new endpoints quicker to end users but I am just saying it doesn't need to stay exclusively in Beta modules.

Let me know what you think, maybe I haven't considered other aspects.

[andyleejordan]

@StevenBucher98 I can't edit your post but can you add VS Code January stable release?

[StevenBucher98]

In case you are looking for next months agenda we are trying out a discussion tab instead of issue tab, Feb 2023 can be found here: https://github.com/orgs/PowerShell/discussions/18986

[ili101]

In case you are looking for next months agenda we are trying out a discussion tab instead of issue tab, Feb 2023 can be found here: https://github.com/orgs/PowerShell/discussions/18986

Updated https://github.com/PowerShell/PowerShell/discussions/categories/community-call