Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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
AdditionalParameterseither until an earlier iteration of js identity, but we can probably remove it now as well.