Skip role assignment handling for emulators

[davidfowl]

Description

• Updated BuildRoleAssignmentAnnotations to skip processing for container emulators.
• Added a new test DoesNotApplyRoleAssignmentsInRunModeForEmulators to verify that role assignments are not applied to emulator resources.

Fixes #9422

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
• Did you add public API?
  • No
• Does the change make any security assumptions or guarantees?
  • No
• Does the change require an update in our Aspire docs?
  • No

[Copilot]

Pull Request Overview

This PR updates the role assignment handling logic to skip processing for container emulator resources and adds a corresponding unit test to verify this behavior.

• Skips role assignment processing for emulator resources in AzureResourcePreparer.
• Adds a dedicated test to ensure that role assignments are not applied for emulator resources in run mode.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
tests/Aspire.Hosting.Azure.Tests/AzureResourcePreparerTests.cs	Added test DoesNotApplyRoleAssignmentsInRunModeForEmulators verifying skip behavior for emulator resources.
src/Aspire.Hosting.Azure/AzureResourcePreparer.cs	Updated BuildRoleAssignmentAnnotations to bypass processing for resources identified as containers.

Comments suppressed due to low confidence (1)

src/Aspire.Hosting.Azure/AzureResourcePreparer.cs:151

• [nitpick] Consider renaming the method 'IsContainer()' to a more explicit name (e.g., 'IsContainerEmulator()') to clarify that it checks for emulator resources, thereby improving code readability.

if (azureReference.IsContainer())

[davidfowl]

/backport to release/9.3

[github-actions]

Started backporting to release/9.3: https://github.com/dotnet/aspire/actions/runs/15469706213

[github-actions]

@davidfowl backporting to "release/9.3" failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Skip role assignment handling for emulators
Using index info to reconstruct a base tree...
M	src/Aspire.Hosting.Azure/AzureResourcePreparer.cs
M	tests/Aspire.Hosting.Azure.Tests/AzureResourcePreparerTests.cs
Falling back to patching base and 3-way merge...
Auto-merging tests/Aspire.Hosting.Azure.Tests/AzureResourcePreparerTests.cs
CONFLICT (content): Merge conflict in tests/Aspire.Hosting.Azure.Tests/AzureResourcePreparerTests.cs
Auto-merging src/Aspire.Hosting.Azure/AzureResourcePreparer.cs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Skip role assignment handling for emulators
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

[eerhardt]

Thanks!

[davidfowl]

@eerhardt can you backport this change to 9.3?

[eerhardt]

@eerhardt can you backport this change to 9.3?

Yes. Will do.

[danmoseley]

Patched in 9.3.1. To pick up this fix if you need it,

For existing projects targeting 9.3.0, please update as follows;
<Sdk Name="Aspire.AppHost.Sdk" Version="9.3.0" /> to <Sdk Name="Aspire.AppHost.Sdk" Version="9.3.1" /> and
<PackageReference Include="Aspire...." Version="9.3.0" /> to <PackageReference Include="Aspire...." Version="9.3.1" /> and restore packages.

If you're creating new projects, you can just install and use the updated project templates: dotnet new install Aspire.ProjectTemplates::9.3.1 --force