PoshRocket 1.1: Credential Profiles & Job Import/Export
PoshRocket 1.1 is out, and it adds two things people have been asking for since day one: a way to hand scripts real credentials without hardcoding them, and a way to move a job from one machine to another without rebuilding it by hand.
Credential profiles
A lot of scheduled scripts need to authenticate to something — PowerCLI against vCenter, Exchange Online, Microsoft Graph, AWS, Azure. Until now, that meant hardcoding secrets into the script itself or building your own credential-handling workaround.
Credential profiles fix that. Create a named profile (say, Azure-Prod), give it
whatever key/value fields your script needs, and link it to a job. At run time, PoshRocket
decrypts the profile and injects each field as an environment variable, so your script just
reads $env:ClientSecret like any other environment variable — no special API,
no PoshRocket-specific code in your script at all.
Values are encrypted at rest on your machine (Windows DPAPI) and never appear in job configs, logs, or run history. Full walkthrough with examples in the Credentials docs.
Job import/export
Setting up the same job on a second machine used to mean recreating it by hand. Now you can
select a job, click Export Job, and get a single .zip with the
job's settings and its script file. Import Job on the other end brings it
back — script included — ready to run.
If the job used a credential profile, the export carries over the profile's name and field names only, never the encrypted values (which are tied to the machine they were created on anyway). On import, PoshRocket offers to help you set up a matching profile with fresh values right there. Details in the Import/Export docs.
Get it
Download the latest installer from the Releases page. It upgrades an existing install in place — same install location, same service registration — and keeps your jobs, history, and license activation intact.