-
Notifications
You must be signed in to change notification settings - Fork 129
Community Call March 18th, 2021 #280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can demo my gMSA cmdlet https://github.com/Ryan2065/gMSACredentialModule Get's a usable PSCredential object from a gMSA name and has an Invoke command to make running commands easy. Windows PowerShell only but works in 5 and 7. |
Hello, I can demo vSphereDSC (PowerShell DSC resources for VMware) https://github.com/vmware/dscr-for-vmware/wiki There are 73 DSC resources to build and config the VMware vSphere environment. We have also leverage Invoke-DSCResource to execute DSC resources without involving the PowerShell LCM engine. |
I could demo my new Microsoft.Graph.PlusPlus module. |
I could talk about how I created this: https://blog.jongallant.com/2021/03/organize-photos-powershell/ |
Like to add:
|
Sorry, we dropped the ball on this one. For tomorrow, we'll just go ahead with Justin's demo. We will create an Office Form where people can sign up as we need to get email addresses to invite external folks to the presentation side of the Teams meeting. |
The PowerShell Core Chocolatey Package is now automatically built at https://gitlab.com/guided-explorations/microsoft/chocolatey/powershell-core using GitLab shared runners. It doubles as an example of doing this for organizations and open source packagers that want to do the same. Since the preview package published on the same github release page - they would end up going there now rather than being on the separate chocolatey id "powershell-preview" Would this cause any foreseeable issues with existing automation out in the community? |
There was a good discussion on Twitter about potentially shipping pwsh in-box to the Windows Semi Annual Channel build, but just not LTSC, since Semi-Annual Channel uses the modern lifecycle which is compatible with the dotnet one. Any thoughts there? Maybe just in-boxing the windows store version as a default? |
Have a small and simple PR pending for review :-) : PowerShell/PowerShell#14830 |
Are Crescendo github discussions stopped ? Would like to do share some ideas there. |
Please feel free to start a new discussion! They are open. |
There are two :-) |
Apparently Windows 10 Calendar is bad at calculating daylight saving from ics files. |
Uh oh!
There was an error while loading. Please reload this page.
Agenda:
$profile
We're open to 1 or 2 more demos from the community. Reply here with what you want to demo and it'll be first come, first served (if approved). Demos are limited to no more than 5 mins each. Intent is to show some neat things happening in the PowerShell community!
Please reply with questions and other topics you'd like to see covered in our next community call.
The text was updated successfully, but these errors were encountered: