Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions eng/common/TestResources/New-TestResources.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -709,6 +709,7 @@ $serialized
# Set global variables that aren't always passed as parameters
`$ResourceGroupName = `$parameters.ResourceGroupName
`$AdditionalParameters = `$parameters.AdditionalParameters
`$ArmTemplateParameters = `$parameters.ArmTemplateParameters
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copying over from https://github.com/Azure/azure-sdk-for-js/pull/37736/changes#r2989926543

What is currently done in other comparable tests is that post-script inspects the arm template deployment outputs only. I think this is a better approach because it reduces any coupling on parameters/variables that have to be consistently named and passed across yaml, powershell and arm/bicep files. For example: https://github.com/Azure/azure-sdk-for-net/blob/0acbe6a297f69e026e78a93ba6df1bf89af866a0/sdk/keyvault/test-resources-post.ps1#L36-L39

When I selected the parameters to copy over I only picked ones that were actively used across all our post scripts. I originally didn't include AdditionalParameters either until an earlier iteration of js identity, but we can probably remove it now as well.

`$DeploymentOutputs = `$parameters.DeploymentOutputs
$postDeploymentScript `@parameters
"@
Expand Down