Rename historical job API endpoints to threat hunting #991
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
api-clients-generation-pipeline
bot
requested a review
from a team
as a code owner
api-clients-generation-pipeline
bot
requested a review
from a team
as a code owner
api-clients-generation-pipeline
bot
force-pushed
the
datadog-api-spec/generated/4508
branch
from
a606cf3 to
19f929a
Compare
skarimo
approved these changes
Oct 27, 2025
api-clients-generation-pipeline
bot
deleted the
datadog-api-spec/generated/4508
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See DataDog/datadog-api-spec#4508 Test branch datadog-api-spec/test/mael.gaonach/rename-historical-job-endpoints