Skip to content

draft: add implied version support ranges to integration registry #13287

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: conti/integration-registry-versioning
Choose a base branch
from

Conversation

wconti27
Copy link
Contributor

Checklist

  • PR author has checked that all the criteria below are met
  • The PR description includes an overview of the change
  • The PR description articulates the motivation for the change
  • The change includes tests OR the PR description describes a testing strategy
  • The PR description notes risks associated with the change, if any
  • Newly-added code is easy to change
  • The change follows the library release note guidelines
  • The change includes or references documentation updates if necessary
  • Backport labels are set (if applicable)

Reviewer Checklist

  • Reviewer has checked that all the criteria below are met
  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Newly-added code is easy to change
  • Release note makes sense to a user of the library
  • If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
  • Backport labels are set in a manner that is consistent with the release branch maintenance policy

)
for integration_name, integration_version in incompatible_integrations.items():
# set environment variable to disable integration
os.environ["DD_TRACE_" + integration_name.upper() + "_ENABLED"] = "false"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 Code Quality Violation

use f-string or .format to format strings (...read more)

Concatenation of multiple strings is not efficient and make the code hard to read and understand.

Instead of concatenating multiple strings, use an f-string or a format string.

Learn More

View in Datadog  Leave us feedback  Documentation

Copy link
Contributor

CODEOWNERS have been resolved as:

ddtrace/contrib/integration_registry/registry.yaml                      @DataDog/apm-core-python @DataDog/apm-idm-python
lib-injection/sources/sitecustomize.py                                  @DataDog/apm-core-python
scripts/freshvenvs.py                                                   @DataDog/apm-core-python
scripts/generate_table.py                                               @DataDog/apm-core-python
scripts/integration_registry/_update_integration_registry_versions.py   @DataDog/apm-core-python
supported_versions_output.json                                          @DataDog/apm-core-python
supported_versions_table.csv                                            @DataDog/apm-core-python

Copy link
Contributor

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 235 ± 4 ms.

The average import time from base is: 236 ± 4 ms.

The import time difference between this PR and base is: -0.9 ± 0.2 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.883 ms (0.80%)
ddtrace.bootstrap.sitecustomize 1.213 ms (0.52%)
ddtrace.bootstrap.preload 1.213 ms (0.52%)
ddtrace.internal.products 1.213 ms (0.52%)
ddtrace.internal.remoteconfig.client 0.611 ms (0.26%)
ddtrace 0.670 ms (0.28%)

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.

1 participant