Skip to content

Conversation

@bkizer-tenable
Copy link

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • tools/python/requirements.txt

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Deserialization of Untrusted Data

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-AZURECORE-14927372
@bkizer-tenable
Copy link
Author

Merge Risk: Medium

This minor version upgrade of azure-core introduces breaking changes related to the optional OpenTelemetry tracing functionality.

  • Tracing Enablement: Automatic enablement of the OpenTelemetry plugin is removed. Tracing must now be explicitly enabled by setting settings.tracing_implementation to \"opentelemetry\". [7]
  • Span Naming: The default span name in DistributedTracingPolicy no longer includes the URL path, now only containing the HTTP method (e.g., "GET") to align with OpenTelemetry conventions. [7]

These changes only affect applications that have configured custom OpenTelemetry tracing.

Source: Azure SDK for Python Changelog
Recommendation: If you use OpenTelemetry tracing with the Azure SDK, verify your configuration to ensure tracing is still enabled and that you are not dependent on the previous span naming format.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants