[PREVIEW COPY] Update cloud-rules-api.mdx #21466
Closed
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.
Mirror PR Summary
This is a preview copy of PR #21456 from @ydeshpande-ai, created at 2025-08-12 11:36:59 IST.
Original PR Details
patch-1
ydeshpande-ai-patch-1
95d7cd8521555573e0ec39785a1ddcfa8a5d3af7
(95d7cd8)Original PR Description:
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
What problems does this PR solve?
This PR provides public documentation for updating existing Pipeline Cloud Rules via the NerdGraph API. Previously, there was no official guidance on how users could modify their existing cloud rules programmatically. This could resolve the gap for users who needed to adjust their data filtering rules over time (e.g., change the NRQL, description, or name) without having to delete and recreate them.
Add any context that will help us review your changes such as testing notes, links to related docs, screenshots, etc.
This new documentation enables users to manage their Pipeline Cloud Rules more flexibly. The update functionality was recently enhanced to ensure that all rule properties are correctly updated in the backend when the NRQL changes. This means users can now reliably modify their rules to adapt to evolving data ingestion needs. Below is the screenshot of the working endpoint that we tested out on internal-api for NerdGraph. For more ref: #21455