Azure / Azure/bicep-deploy

CorrelationId logged is the correlationId for the most recent polling request, not the original deployment

Open
#179 0 comments 0 reactions 0 assignees View on GitHub
Area - Error Handling bug
Dominant language
TypeScript
Stars
64
Forks
20
Avg merge
15h 37m
Merged PRs (30d)
4

Description

This makes troubleshooting difficult if someone shares errors, because the correlationId doesn't match what we see in the logs.

Instead, we should set the correlationId when making the initial request in the SDK.

Contributor guide

Open the contributing guide

Research direction

Start by locating the SDK code that makes the initial deployment request and the later polling requests, then trace where correlationId is stored and logged. Verify the behavior with the existing tests or request a reproduction if no test is named. Done means errors report the initial deployment correlationId rather than the most recent polling request's ID.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.