Skip to content

Enhance deployment error messages with resource context#18767

Open
igrapel wants to merge 3 commits intoAzure:mainfrom
igrapel:feature/enhanced_deployment_error
Open

Enhance deployment error messages with resource context#18767
igrapel wants to merge 3 commits intoAzure:mainfrom
igrapel:feature/enhanced_deployment_error

Conversation

@igrapel
Copy link
Copy Markdown

@igrapel igrapel commented Jan 2, 2026

Description

Enhance deployment error messages to include resource context, providing more informative output when ARM deployments fail. This improves debugging and clarity for users by showing symbolic names, resource types, and resource names alongside error codes and messages.

Example Usage

When a deployment operation fails, the error message now includes resource context:

Resource 'mySymbolicName' (Microsoft.Foo/bar 'myResource'): BadRequest: Something went wrong.

This replaces generic messages that only included the error code and message.

Checklist

Microsoft Reviewers: Open in CodeFlow

@majastrz
Copy link
Copy Markdown
Member

@igrapel Can you clarify which deployment messages are being fixed here? Is this purely for local deploy?

@igrapel
Copy link
Copy Markdown
Author

igrapel commented Feb 19, 2026

@igrapel Can you clarify which deployment messages are being fixed here? Is this purely for local deploy?

Hi, I no longer see the PR that I attempted to solve last month. From what I remember, the goal was to include resource context (symbolic name/type/name) when a deployment fails. I don't think it was supposed to be local.

@majastrz
Copy link
Copy Markdown
Member

That's the part that confused me because the source code for the deployment engine is internal, so non-local deployments can't be fixed with a PR on GitHub unfortunately.

@igrapel
Copy link
Copy Markdown
Author

igrapel commented Feb 20, 2026

That's the part that confused me because the source code for the deployment engine is internal, so non-local deployments can't be fixed with a PR on GitHub unfortunately.

I vaguely remember that I was trying to solve an issue relating to error messages not being sufficiently specific. Is it possible the underlying issue was removed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants