Propagate resource tags to implicit child resources #22176

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

In v17, when adding a tag to a resource in code, the tag is currently only applied to that resource and not to its implicit child resources.

For example, when using WithNpm() to add an npm build resource to a JavaScript resource, applying a tag to the parent resource does not automatically apply it to the generated npm build resource.

This creates an inconsistent experience in the Aspire Dashboard.

When filtering resources by tag, the parent and its implicit child resources can become disconnected because only one of them matches the filter. As a result, the relationship between the resources is no longer immediately visible.

Describe the solution you'd like

When a tag is applied to a resource, automatically propagate that tag to its implicit child resources.

For example:

Apply a tag to a JavaScript resource.

Its implicitly created npm build resource should receive the same tag.

Filtering by that tag in the Dashboard should show both resources, preserving their parent-child relationship.

Ideally, this behaviour would be consistent across all implicitly created child resources, rather than being specific to npm build resources.

Additional context

This is particularly relevant when organising larger Aspire applications using tags to group resources by application, domain, or functional area.

The goal is to ensure that filtering by a tag does not break the logical grouping and visibility of resources that belong together.