🐛 FIX #52676 update sentry scope configuration to remove deprecation wa…

[saimadib]

…rning

Fixes #52676

What

• Addresses deprecation warning that appears in build logs when building airbyte-ci/connectors/pipelines for testing
• Updates the Sentry SDK scope configuration to use the new recommended API
• Removes warning: sentry_sdk.configure_scope is deprecated and will be removed in the next major version

How

• Modified sentry_utils.py to use get_current_scope() instead of deprecated configure_scope()
• Updated the with_step_context decorator to follow Sentry SDK's new best practices
• Maintains existing functionality while using the new API

Review guide

1. airbyte-ci/connectors/pipelines/pipelines/helpers/sentry_utils.py

• Key change is replacing configure_scope() with get_current_scope()
• Verified all existing context and tags are preserved
• Test by running poetry run pytest . in the pipelines directory

User Impact

• Removes deprecation warnings from build logs
• No functional changes - all existing Sentry functionality remains the same
• Prepares code for future Sentry SDK versions

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

[vercel]

@saimadib is attempting to deploy a commit to the Airbyte Growth Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[Charlesnorris509]

Hey @saimadib I think you did great to resolve this issue but I would Add a docstring to explain the purpose of the with_command_context decorator to enhance readibility. Using a decorator to set Sentry context for pipeline commands is a good way to encapsulate this logic.

[saimadib]

Hi @Charlesnorris509 , thanks for the feedback! I've updated the PR to include a docstring for the with_command_context and with_step_context decorator, which should enhance readability. Let me know your feedback!.

[Charlesnorris509]

The updated code looks great! The detailed docstrings make it much clearer and more structured, and the integration of Sentry for error tracking and context management is well done. The docstrings really help with readability and maintainability. Additionally I test the integration locally and it seems like you passed the 'ruff-format' test. I'll Approve the change. But i would recommend preparing some procedure for Handling missing attributes and writing unit tests would further improve the robustness and reliability of the code