Alex ShtinandGitHub 69e3d20e76 Switch to code gen approach for extracting WorkflowId/RunId log tags (#6331) ...

## What changed?
<!-- Describe what has changed in this PR -->
Switch to code gen approach for extracting WorkflowId/RunId log tags.

## Why?
<!-- Tell your future self why have you made these changes -->
- Code gen approach is more performant and more verbose. 
- Some APIs on workflow service didn't log workflow tags
(`UpdateWorkflowExecution`).
- history and matching services didn't log workflow tags at all (because
workflow tags not on the root level in request). Logging these fields is
very important for debugging.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Added unit tests.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
No risks.

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->
No.

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
No.

2024-09-24 20:24:37 +00:00

..

main_test.go

Switch to code gen approach for extracting WorkflowId/RunId log tags (#6331)

2024-09-24 20:24:37 +00:00

main.go

Switch to code gen approach for extracting WorkflowId/RunId log tags (#6331)

2024-09-24 20:24:37 +00:00