Information about the PowerShell Universal repository.
The configuration data for PowerShell Universal is primarily stored within the repository. By default, the repository folder can be found in
%ProgramData%\UniversalAutomation\Repository. You can adjust the location of the repository by editing the
The repository contains PowerShell scripts and XML files that are produced when using the PowerShell Universal admin console. The repository folder is also watched for changes so any change made on disk will cause the system to reload the file and reconfigure the platform. When using Git integration, the repository folder is what is synchronized with the git remote.
Files stored in the repository are stored as plain text to allow for easy differencing with source control tools.
- Login Pages
- Published Folders
- Rate Limits
These entities are stored within the PowerShell Universal database.
- App Tokens
- Job History
You can edit the repository files directly in the admin console by navigating to Settings \ Configurations. The editor allows you to create files and folders and edit any file within the repository directory.
This script is responsible for defining all the environments within PowerShell Universal.
This script is responsible for defining the license used in PowerShell Universal.
Set-PSULicense -Key "<License></License>"
This script runs before any configuration is done within PowerShell Universal. The server is running but none of the services have started. This is useful for install modules or configuring secret vaults before discovery of those resources are started.
This folder contains the page XML files. These are not intended to be edited manually and should be edited with the page designer.
This script is responsible for configuring tags.
A custom configuration script can be executed within the configuration process. The path to the configuration script can be defined in
appsettings.jsonor as an environment variable.
$Env:Data__ConfigurationScript = "customScript.ps1"
You can chose to return items such as endpoints, scripts or dashboards from the script. Additionally, you can use this script to configure resources like modules and secret vaults before the system is started. The custom configuration script is run before any other configuration scripts.