variables.ps1
configuration file.BuiltInLocalVault
are stored within the Windows Credential Manager instance of the security principal that is running PSU. For example, the service account of the user running the Universal service. If you change users (such as running as a service account), the account will not have access to the previous user's secrets and you will need to add those secrets again.PSUSecretStore
vault is integrated with the Microsoft SecretStore
module to store secrets in a cross-platform file. Ths file is tied to the current user account running PowerShell Universal. The password for the vault is stored in appsettings.json
.-Variable
parameter of New-PSUEnvironment
with a wild card (*). If you are using your own environments, you will have to configure which variables you would like included. You can reference a variable like you would any other PowerShell variable. The variable will contain the value you set. If you use a secret, it will contain the secret's value.-Variable
parameter.$Secret
scope. For example, if you defined a secret named Credential
, you could access that secret anywhere with the secret scope. You cannot set secrets using the secret scope. ForEach-Object
with the -Parallel
parameter, you will need to take advantage of the $using
keyword. PSUSecretStore
PasswordPSUSecretStore
vault password is stored within appsettings.json
in Secrets \ SecretStore \ Password.UAJob
variable