Summary
Some pup commands send raw Datadog requests instead of using the typed client. Those commands are easier to get wrong when the upstream request shape changes.
We recently hit this with dbm samples search: the mocked payload shape did not match the documented Datadog contract.
Proposal
Add a small optional check for raw request shapes.
Requirements:
- skip cleanly when the verification input is not available
- do not block normal OSS development or CI
Initial scope
Start with dbm samples search and verify the expected request shape:
- top-level
list
- documented
sorts structure
Why
This would give us a lightweight guardrail for raw endpoints without adding much maintenance overhead.
Summary
Some
pupcommands send raw Datadog requests instead of using the typed client. Those commands are easier to get wrong when the upstream request shape changes.We recently hit this with
dbm samples search: the mocked payload shape did not match the documented Datadog contract.Proposal
Add a small optional check for raw request shapes.
Requirements:
Initial scope
Start with
dbm samples searchand verify the expected request shape:listsortsstructureWhy
This would give us a lightweight guardrail for raw endpoints without adding much maintenance overhead.