Skip to content

stability: remediate validated findings across core, go, and docs - #28

Merged
tonyredondo merged 4 commits into
mainfrom
fix/findings-remediation
Feb 18, 2026
Merged

stability: remediate validated findings across core, go, and docs#28
tonyredondo merged 4 commits into
mainfrom
fix/findings-remediation

Conversation

@tonyredondo

Copy link
Copy Markdown
Member

Summary

  • Harden sync/uploader behavior and metadata handling with safer normalization, configurable HTTP policy, stricter macro validation, and cross-platform path/command handling updates.
  • Expand regression coverage across core/go/unit/integration tests (including schema tuple items, env/command escaping, mock server behavior, and example dry-run execution) and align CI to execute those paths.
  • Align docs/examples and build metadata with implemented behavior: add docs link checks, refresh config/install/troubleshooting references, normalize terminology, and keep generated/public labels and package marker conventions explicit.

Test plan

  • ./bazelw test //tools/tests/core:tests
  • cd modules/go && ../../bazelw test //tests:tests --override_module=datadog-rules-test-optimization=../..
  • ./bazelw test //tools/...
  • cd modules/go && ../../bazelw test //... --override_module=datadog-rules-test-optimization=../..
  • ./bazelw test //examples/...
  • ./tools/tests/integration/run_mock_server_tests.sh

Apply the validated findings remediation set to harden sync/uploader behavior, close reliability gaps in CI/integration tests, and align user-facing docs/examples with the implemented contracts.
@tonyredondo
tonyredondo requested a review from a team as a code owner February 18, 2026 10:28
@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Feb 18, 2026

Copy link
Copy Markdown

⚠️ Code Quality    ✅ Code Vulnerabilities    ✅ Library Vulnerabilities

Fix all issues with BitsAI or with Cursor

⚠️ Warnings

🛠️ 1 Code quality issue detected

High: python-best-practices/nested-blocks (Fix with Cursor) Do not have too many nested blocks View rule
tools/core/validate_payload_schema.py:226-229

ℹ️ Info

🛡️ No new code vulnerabilities
📚 No new vulnerable libraries detected

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 560e28c | Docs | Datadog PR Page | Was this helpful? Give us feedback!

Comment on lines +226 to +229
if additional_items is False:
errors.append(f"{path}[{idx}]: additional item not allowed")
elif isinstance(additional_items, dict):
_validate(item, additional_items, root, f"{path}[{idx}]", errors)

@datadog-datadog-prod-us1 datadog-datadog-prod-us1 Bot Feb 18, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔴 High: Code Quality Violation

too many nesting levels (...read more)

Avoid to nest too many loops together. Having too many loops make your code harder to understand.
Prefer to organize your code in functions and unit of code you can clearly understand.

Learn More

Fix with Cursor

View in Datadog  Leave us feedback  Documentation

Align maintainer guidance with actual repo test/build entrypoints and add targeted edge-case coverage/documentation to close the final findings audit gaps.
Resolve settings.json discovery in the mock-server harness across Git Bash and Bazel Windows path variants to avoid false negatives in Windows CI.
Create an empty follow-up commit so PR checks re-evaluate on the latest branch head while investigating stale Windows CI status propagation.
@tonyredondo
tonyredondo merged commit 2f4c367 into main Feb 18, 2026
10 checks passed
@tonyredondo
tonyredondo deleted the fix/findings-remediation branch February 18, 2026 12:15
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