Video

can I host ansible in cloud and update windows laptop which are always out of internal network. They are always connected to extrnal network. no vpn

Really cool stuff. Love the toys.😊

## Summary of "Best Practices for Creating PowerShell Modules: A Vendor's Perspective" by Robert Quimbey This CZcams video by Robert Quimbey, a product manager at Pure Storage, shares practical insights on developing PowerShell modules from a vendor's perspective. He emphasizes the importance of building modules that are: **User-Friendly and Troubleshootable:** * **Don't hide modules:** Use built-in PowerShell tools for easy troubleshooting and allow users to find and manage modules easily. * **Provide clear help:** Utilize built-in "Get-Help" functionality and consider Dynamic Help for automatic updates. * **Support multiple versions:** Allow simultaneous installation of different versions of a module and its dependencies. * **Consider backward compatibility:** Handle different API versions and provide ways for users to specify specific API versions. * **Offer alternatives:** Provide CLI options for functionality not yet available in the API. **Automated and Efficient:** * **Automate release notes:** Use scripts to generate release notes automatically by comparing old and new module versions. * **Automate code generation:** Use tools like Swagger to generate module functions from API changes. * **Test thoroughly:** Utilize Pester for unit testing and Jenkins for orchestration of testing. * **Implement robust logging:** Log critical information for troubleshooting and track module usage for development prioritization. **Best Practices for Module Development:** * **Minimize parameter creep:** Avoid adding too many parameters to a commandlet to simplify usage and testing. * **Filter data on the endpoint:** Reduce network traffic and improve performance by filtering data at the source. * **Set reasonable defaults:** Provide default values for parameters and consider providing a configuration file for customization. * **Provide clear examples:** Include sample scripts in the help documentation and on GitHub to demonstrate common use cases. **Key Takeaways:** * Building user-friendly, stable, and efficient PowerShell modules requires careful planning and attention to detail. * Automation is crucial for streamlining development and release processes. * Consider the needs and limitations of your users and the environments they work in when making design decisions. This presentation provides valuable insights and recommendations for developers looking to create high-quality PowerShell modules that are both practical and maintainable.

Thank you I just needed this for my scripts!!

Ever questioned yourself about your abilities as a speaker? Oh boy, that was the least content in the longest speaking time ever - this was essentially a 10 minutes talk blown up to a full hour. And nothing was really new with the possible exception of PS7 optimizations for | out-null... The only takeaway for me was your testing framework which I really like.

Great Learning thanks

Pode is an an amazing framework for building APIs in pwsh.

great talk! I'm a quite experienced linux sysadmin, worked as a windows sysadmin from 2010-2014, although don't really use it much nowadays, still love and miss powershell, I wish it to gain ground in the linux sysadmin space

This is so awesome! Just the timeline option is so useful. Thank you so much.

His book windows PowerShell in action is the Bible in PowerShell

Underrated video, thank Ou

Lets see how close chatgpt can get me to this

Great content, thanks Michael!

he mentions a github in the comments, but no luck :( I was hoping I could grab his testing json entries.

Update the db in apt and source the shell to get a new session in the current session and it would have detected the java RunTime or force it by exporting the RUNTIME variable to the local session in the current shell or force systemd to restart in place (but wsl dont know if systemd is actually there)

What is the best way to protect the password file? Deny file ACLs with disabled inheritance?

e essa barriguinha aí em

Thank your for this great talk! 🙂

donald trump

So are package managers (WinGet, Chocolatey, Scoop, Pacman, etc) meant for system administrators, or do end users (or teams) benefit? For example, a small team developing firmware in which the end customer may upgrade the firmware running on the device?

Phenomenal talk Chris! I've only learned about Redfish earlier this year and it's been great to use. I look forward to pulling the toolkit (and hopefully contributing!).

Excellent Session :)

Awesome!

Great Duo. Nice talk 👍🏻

Nice 👍🏻

Very interesting, thanks for sharing 👍🏻

Man, bummer - it almost seems like it would've been better to risk fixing the resolution even if it ruined the demo, since this demo was the bulk of the presentation and it was unreadable rendering it basically useless anyway.

Good stuff! Love it. 🎉

Is the double-tap to show all available parameters or valid entries a feature only in PS7? There're times he only types '-' and double-taps to show all the possible parameters on a new line, like Linux behavior, but this does not work in VSC PowerShell 5.1 on my Windows machine

ai art is annoying

My system been powershell attacked what should I do now? Please help me fast

Great talk 👌🏻

Good stuff, thanks 👍🏻

The demo Gods really hate you don't they! 10/10 for perseverance and great talk 👍🏻 thanks

Excellent talk 👏🏻

Excellent talk, the best I've watched so far from this year's event. lol @ 2:03:23

mind blowing stuff

It was hard to hear the questions the audience was asking, but I think someone was asking for what I would really like to see in the predictors, which is predictors for command line tools like `docker`, `git` or `kubectl`. It would be great if you could import a bash completion file, since those already exist and are more likely to be kept up to date by the tool makers. I don't want to use something like crescendo to make a PowerShell commandlet for those command line tools. All of the help on the internet is based on the command line tools and the commandlet would just be something else to learn. A good command line predictor would be what might make be replace bash with pwsh on linux. I love PowerShell for scripts (much better than bash script or Python) and I would like to make it my default shell, too.

fabulous, thorough without wasting time over-explaining

good stuff, thx

Learned some interesting tips, but not sure when I'd use some of them. For example, assigning an array of values to a comma delimited list of variables. $var1,$var2,$var3 = 1..10, this would set $var1 an $var2 to the first two in the set of 1 through 10, while the last variable in the list is set to the rest of the values in the array (3 through 10).

Dan Schroeder here, the presenter. Near the end I was asked, "Why do the smoke tests need to be a different file than the Pester tests that we run during the build?" and during the presentation my mind blanked. The main reason that "Invoke-SmokeTests.ps1" is needed is because those smoke tests will be ran against an installed version of the module. The module is actually downloaded from the gallery and installed on the agent during the pipeline, and then the smoke tests are ran against that installed version. This means it will only have access to the public functions exposed by the module. The regular Pester tests that are run as part of the build are ran before the module is compiled into a .nupkg file, and can reference private functions not exposed by the module if needed. If we tried to run the regular build-time Pester test files as part of the smoke tests, depending on the tests, they may fail due to not being able to find some private functions.

czcams.com/video/xUXDYn_4rzw/video.html

Nice talk, build from history to the present

Very nice presentation 👍👍👍

I can hear the Enter key crying.

great dayi

Wow, he literally said you cannot audit mouse clicks. You most certainly can audit mouse clicks and as a matter of fact, I can record entire user sessions down to the keystrokes.

Here are some of the key best practices covered in the presentation: 1. Proper naming conventions - Use approved verb-noun naming, pascal case, singular nouns for parameters. 2. Parameter validation - Use parameter validation attributes like Mandatory, ValidatePattern, ValidateScript to ensure proper input. 3. Error handling - Implement try/catch blocks and $ErrorActionPreference to handle errors gracefully. 4. Pipeline input - Support ValueFromPipeline/ValueFromPipelineByPropertyName as needed. 5. Multiple parameter sets - Use ParameterSetName attribute to create multiple parameter sets. 6. Avoid unnecessary code - Keep functions focused on a single task. Avoid aliases, positional parameters in shared code. 7. Commenting - Use comment-based help, verbose output instead of inline comments. 8. Modularity - Create reusable tools by writing functions in script modules with manifests. 9. Formatting output - Use PowerShell formatting files to nicely format function output. 10. Source control and unit testing - Use source control like Git and Pester for unit testing. 11. Simplicity - Strive for simplicity and clarity in code design. The overall emphasis is on writing clean, testable, reusable and maintainable PowerShell code following community best practices.

Glad to see I follow most of these practices already, though I didn't know about the $array += optimisation, I went back to my old scripts and modified them, they run much better now.