[pull] master from DataDog:master#499
Merged
Merged
Conversation
Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com>
* adding troubleshooting doc link * Add changelog entry and apply black formatting
* Fix validate-skip-qa workflow to avoid running in pull_request_target * Move skip-qa comment rendering to GitHub action Made-with: Cursor * Clean up skip-qa comment renderer to use string.Template * Move skip-qa comment posting to workflow_run-triggered workflow - validate-skip-qa.yml drops id-token: write and dd-octo-sts; it only renders the comment body and uploads it as a pr-comment artifact. - post-pr-comment.yml (new) runs on workflow_run, always from master, and cannot be modified by fork PRs. It resolves the PR number from the event (not from the artifact), validates the comment marker, exchanges OIDC via dd-octo-sts, and posts the comment. - STS policy is pinned to post-pr-comment.yml@refs/heads/master with issues: write only; the old validate-skip-qa policy is removed. * Defer post-pr-comment workflow and policy to #23415 The central workflow_run poster and its trust policy are being landed in their own PR so they reach master first. Once #23415 merges, this PR's validate-skip-qa.yml will start producing comments through the central poster end-to-end. * Drop marker ownership from the skip-qa producer The central post-pr-comment.yml now derives the comment marker from the triggering workflow's display name and prepends it to body.md, so the producer no longer emits or tracks a marker of its own. Remove the marker line from the two Template bodies and delete the workflow step that wrote meta.json. The artifact now contains only body.md. * Log skip-qa inputs for easier debugging * Update dependency resolution * Revert the spurious dependency resolution * Fix accidental removal during rebase * Update dependency resolution * Revert "Update dependency resolution" This reverts commit 0a3f24d. --------- Co-authored-by: dd-agent-integrations-bot[bot] <dd-agent-integrations-bot[bot]@users.noreply.github.com>
* Bump cryptography from 46.0.6 to 46.0.7 Addresses CVE-2026-39892 (VULN-62136). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Kyle-Neale <kyle.neale@datadoghq.com> * Add changelog entries for cryptography bump Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Kyle-Neale <kyle.neale@datadoghq.com> * Update dependency resolution Signed-off-by: Kyle-Neale <kyle.neale@datadoghq.com> * Update dependency resolution --------- Signed-off-by: Kyle-Neale <kyle.neale@datadoghq.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: dd-agent-integrations-bot[bot] <dd-agent-integrations-bot[bot]@users.noreply.github.com>
…er (#23352) The dry-run flag was temporarily forced to true pending an update to agent-integration-wheels-release. That update has landed, so flip the default back to false so push-triggered runs on master and X.Y.x branches actually dispatch wheel builds. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…ent 404 (#23462) * Fix nutanix conftest: pytest.fail on unregistered URLs instead of silent 404 * Move requests import to module level in test_configuration.py * Remove transport-specific regression test for conftest fallthrough
* Adding parts and merges support
* Cleanup comments
* Address codex comments
* Fixing CI
* Make stalled-merge and stuck-replication thresholds configurable
Expose STALLED_MERGE_ELAPSED_THRESHOLD_SECONDS and
STUCK_REPLICATION_NUM_TRIES as parts_and_merges config options so
operators can tune them to match their cluster behaviour without
rebuilding the integration.
parts_and_merges:
stalled_merge_elapsed_threshold_seconds: 3600 # default: 1 h
stuck_replication_num_tries: 3 # default: 3
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Address comment around payload schema
* Adding two new thresholds for merge times
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
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 Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )