A fairly significant update, 1.1’s Mac component leverages AppleScript’s Choose File so you can select multiple PowerShell files to sign at once. It took a bit longer than I thought it would because while you can create generic list objects in PowerShell functions, what gets returned is a generic array. Sigh.
Anyway, it’s up at https://www.powershellgallery.com/packages/Set-PowerShellScriptSig/1.1, and works on both Windows and macOS.
Not a huge one, added iBridge data, so it now shows SIP/SSV/secure boot status, few other things. There’s not much to it if you’re running on Intel, most of this is AppleSilicon only. Available from the PowerShell Gallery at https://www.powershellgallery.com/packages/Get-MacInfo and the github site https://github.com/johncwelch/Get-MacInfo has been updated as well.
Pretty much what it says, GetChooseFileName is now up on the PowerShell Gallery: https://www.powershellgallery.com/packages/Get-ChooseFileName
W00t!!
Both modules are finally published so they can be installed the “right” way!
Get-Help is your friend and there’s documentation on their respective Github repo pages, available via the “Project Site” links for the respective projects
I have the BEST post titles, right?
Now that I have Get-MacInfo working correctly on both Intel and Apple Silicon Macs, it was time to post it to the PowerShell Gallery so that it can be installed the correct way for PowerShell modules. Like everything, there’s a process, but it’s not an awful one. Note that this builds on my previous post about creating my first PowerShell module.
The first step here is to create an account on the PowerShell Gallery and get an access token. Both are pretty straightforward, especially if you have an MS365 account you can use for this already. The only weirdness is the PS Gallery uses Gravatar for your profile picture, which is like…Gravatar still exists? It does, and PS Gallery uses it for your profile pic!
Before submitting, you want to make sure you have the module folder with at least the psm1 and psd1 files in it and ready to go.
The next step is to run the psm1 file through the PowerShell Static Analyzer, PSScriptAnalyzer. To install: Install-Module -Name PSScriptAnalyzer, then to run: Invoke-ScriptAnalyzer <path to psm1 file>.
Most of what I get is fussing about using Invoke-Expression (necessary in my case), using Write-Host, (you can usually replace with Write-Output), and trailing whitespace at the end of a line. Fix the stuff that makes sense to fix.
Next, you’ll want to test the manifest, the psd1 file with Test-ModuleManifest <path to psd1 file>, and fix any errors in that. The manifest is important to the PS Gallery. Some PS Gallery-specific things:
If you have any standalone ps1 files in your module, use Test-ScriptFileInfo on those.
Install .NET for macOS. You have to have this to publish to PS Gallery. You also have to have the path to the dotnet command in your path. The installer for the Current version of .Net is available at https://dotnet.microsoft.com/en-us/download/dotnet, install it, and then add it to your path, most likely in ~/.zprofile. The path I used for it was /Users/<username/.dotnet but any path to the correct dotnet command will work.
Now we’re ready to publish! The command to do so is pretty simple, it’s: Publish-Module -Path <path to module folder> -NuGetApiKey <pat you get from PS Gallery>
Assuming no massive problems in your script, it shouldn’t take too long, et voila, you have a module in the gallery!
That’s really all there is to it. If you update the module, make sure to change the version number and the release notes in the manifest and re-run Publish-Module.
Bynkiidotcom 