Include resource name in 'unsupported resource type' error

[BrennanConroy]

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.

I was trying to azd up an aspire app and getting the following error:
ERROR: generating bicep from manifest: unsupported resource type: executable.v0
That doesn't really mean anything to me, and so I had to go figure out how to generate the manifest so I could search it for executable.v0 and find what resource was failing.

Describe the solution you'd like

It seems like it should be fairly simple to include the resource name that failed.

e.g.
ERROR: generating bicep from manifest: webui is an unsupported resource type: executable.v0

Additional context

Stretch goal; seems like we could also mention adding .PublishAsDockerFile() to the resource in the apphost?

[davidfowl]

@vhvb1989 The error message here could do with some polish and include the resource name.

[vhvb1989]

@davidfowl , I wonder if, from a Publisher perspective, an Azure Publisher should fail when something is detected as non-compatible with Azure as described by the AppHost.

I think running dotnet ..... --publisher azure should fail sooner than AZD getting into it.

For the manifest publisher, I wonder what the plans are? Will you deprecate it? or will you make it Azure-specific?

I can improve the error message for AZD+manifest-publisher, but I am thinking it might not take much until this is replaced for some publisher which would make sure things are well generated for Azure (AZD)