Once a runner is registered in CloudRadial AutomationAI, you install it into your own Azure subscription with a setup package downloaded from the Runners page. This article covers downloading the package, running the installer, the key parameters, and how the runner secret is handled. It is for the technician performing the install.
- Download the Setup Package
- Run the Installer
- Key Parameters
- Entering the Runner Secret
- Previewing and Re-Running
Download the Setup Package
From the Runners page, download the setup package for your runner. The package is a ZIP named for the runner's friendly name, and it contains:
Install-AutomationsRunner.ps1— the one-command installer, generated for your specific runnerrunner-sample/— the deployment template the installer wrapsREADME.md— the setup steps and the full deployment reference
The package is credential-free. It embeds the runner identity, region, version, and instance count for your runner, but it does not contain the runner secret. Extract the full ZIP before running anything.
Run the Installer
Sign in with Az PowerShell, then run the installer:
Connect-AzAccount
./Install-AutomationsRunner.ps1
The installer checks that the Az module is present and that you are signed in, prompts for the runner secret, then provisions everything in your subscription. Run it with -? for the full, current parameter list and examples.
Key Parameters
The installer defaults the embedded values for your runner, so most installs need no parameters. The ones you are most likely to set:
-SubscriptionId— the Azure subscription to deploy into. Optional; omit it to choose from a numbered list of the subscriptions your login can access-ResourceGroup— the resource group name, created if absent. Defaults tocrautomationai-rgso all runner resources stay together-Location— the Azure region for the runner resources, defaulted from your runner's configuration-InstanceCount— how many instances the runner pool should have. Defaults to the count the package was generated for. See the article on scaling runner instances
To change the resource group or location:
./Install-AutomationsRunner.ps1 -SubscriptionId <guid> -ResourceGroup my-rg -Location eastus
The hosting plan (Premium or Flex Consumption) and the AI provider are set from your runner's configuration. To choose the OpenAI provider from a fresh install, run the underlying runner-sample/Deploy-Runner.ps1 directly, which exposes the OpenAI parameters the installer does not. See the article on choosing the runner AI provider.
Entering the Runner Secret
The installer prompts you to paste the one-time runner secret that was shown once at registration:
Paste the runner secret (shown once at registration)
The prompt reads the value as a secure string, so it is not echoed to the screen and is never written to disk. The secret is stored only in the runner's Azure Key Vault, in the resource group you deployed into. If you did not save the secret at registration, you can rotate it by re-running the installer and pasting a new value; the prior secret stays valid for 24 hours.
Previewing and Re-Running
Add -WhatIf to preview the deployment without applying any changes. The installer is fully idempotent, so re-running it converges your runner to the values you pass — it is safe to run again to change settings, scale, or recover from an interrupted install.
Comments
0 comments
Please sign in to leave a comment.