As an long delayed experiment, I installed Windows 10 on my machine and forced myself to use it and go through initial hurtles in order to give it fair chance, see where it stands today as opposed to few years ago when I’ve last tried it and in order to learn few things among everything else. I’ve been using Linux exclusively on my private machines for years, and for work I’ve used Linux and MacOS....
Just like Bash on Linux, PowerShell on Windows has it’s PATH-like variable from which modules are being automatically loaded. To find out array of your paths you can use: PS C:\Users\ivant> $env:PSModulePath D:\Ivan\Documents\PowerShell\Modules;C:\Program Files\PowerShell\Modules;c:\program files\powershell\7\Modules;C:\Progra m Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules Now, I have already experimented a bit with PowerShell but I’ve used Windows PowerShell (different version than Core) and I’ve written a module for it which I’d very much like to continue using in PowerShell Core as well....
Seems to me that this my little trip to the Windows land might actually trigger me to learn a thing or two about that OS. Naturally, I’m also planning to jot those things down here. So while installing Windows to spare NVMe drive it decided to place its bootloader to existing EFI partition where up until then only Fedora had its EFI image. This behavior doesn’t suits me as I can’t offline drive while in windows and then pass it through to the Hyper-V machine (long story…)....
I’ve since evolved this script a bit and have published it on GitHub: https://github.com/ivantomica/AWSVault To log in into AWS I prefer to use small function which calls aws-vault utility and gets URL to login to specific AWS account and then opens that AWS account in its own container tab in Firefox. Reason for this is that my natural habitat is terminal, or textual interface in general, so invoking thing from there instead of doing 20 clicks through interface somehow feels better to me....