Parameter file token replacement #1383
Replies: 1 comment
|
Hey Nate (@nathanfranz) that would be a way. But I can do you one better: You can use the See the following example: . '.\ResourceModules\utilities\tools\Test-ModuleLocally.ps1'
$TestModuleLocallyInput = @{
templateFilePath = '.\ResourceModules\arm\Microsoft.CognitiveServices\accounts\deploy.bicep'
parameterFilePath = '.\ResourceModules\arm\Microsoft.CognitiveServices\accounts\.parameters\speech.parameters.json'
PesterTest = $false
ValidationTest = $false
DeploymentTest = $true
ValidateOrDeployParameters = @{
Location = 'westeurope'
ResourceGroupName = 'validation-rg'
SubscriptionId = 'a7439831-1111-1111-1111-4aa863c96556'
ManagementGroupId = '3d9faf2f-1111-1111-1111-156ee64ba23b'
RemoveDeployment = $false
}
AdditionalTokens = @{
deploymentSpId = 'e58511af-1111-1111-1111-6a10271cfb83'
tenantId = '449fbe1d-1111-1111-1111-4fd5cf25b014'
}
}
Test-ModuleLocally @TestModuleLocallyInput |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
How can the token replacement for the parameter files be achieved before running template deployment through Azure Powershell or CLI? There is a Convert-TokensInFile.ps1 script in the repo. Can this be used to update parameter files and then run a deployment through local command line?
All reactions