Skip to content

I21.2 · More Datadog sources #187

Open

Description

@adssib

Part of #185

Story

As a developer who uses Datadog's API clients or tracers, I want patch-it to watch Datadog's other official sources, not only the one it reads today, so changes in those also reach my code as a fix.

Missing sources

Proposed; check each before writing it (verify, don't guess; leave TBD if unknown). Ids follow the provider/source form (I19.2).

  • datadog/api-client-python · kind changelog · layer sdk · DataDog/datadog-api-client-python CHANGELOG.md: breaking client changes (the API spec is already watched)
  • datadog/ddtrace-python · kind changelog · layer sdk · DataDog/dd-trace-py release notes: removed integrations and settings per major
  • datadog/ddtrace-js · kind changelog · layer sdk · DataDog/dd-trace-js release notes: the same for Node

Subtasks

  • For each source: link, date checked, why it's the best source and a short quote, in providers/datadog.md under Why this source
  • One source per PR, registered under the existing Datadog provider
  • Saved copies in testdata/ (row in testdata/README.md: URL, date fetched, license, quote), a golden file, and one drop test
  • The source lists its versions (I19.8) where its kind supports it
  • make check passes

Acceptance criteria

  • Each new source emits events with source_url and an exact source_excerpt
  • The drop test produces no event
  • The provider page lists every source with its date checked
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions