[CCR-3653] Split Cost Optimization Automation and Notification docs - #38993
Open
zeinageb wants to merge 12 commits into
Open
[CCR-3653] Split Cost Optimization Automation and Notification docs#38993zeinageb wants to merge 12 commits into
zeinageb wants to merge 12 commits into
Conversation
…tomation docs Splits notification rules into their own page (automated_notifications.md), matching the Notification/Remediation tabs in the Automations UI, and updates the Cost Optimization Automation page with the current recommendation type coverage, prerequisites, and setup steps.
Contributor
Author
|
/review |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🤖 Automated review by Claude. AI-generated; verify before acting.
Two small suggestions inline. One additional note that isn't inline-commentable: the cost_optimization_automation.md page title was renamed to the plural (Cost Optimization Automations), but the sidebar menu entry at hugo/config/_default/menus/main.en.yaml:4225 still reads - name: Cost Optimization Automation (singular). Consider updating the menu name to match the new page title so the sidebar link matches the page's H1 and the reference on the _index.md overview.
Reviewed f0853a930b1c44a9e816663b7041bcc2c55913e1 — workflow run
…efs, match menu name to page title
zeinageb
marked this pull request as ready for review
August 7, 2026 13:15
jhgilbert
added
the
astro-reorg-no-conflicts
Points the mako template load at hugo/local/bin/py/, and updates the content/en/ path matching to also accept the hugo/ prefix so preview links resolve for files under the post-reorg layout.
Contributor
Preview links (active after the
|
Renames automated_notifications.md to notifications.md, since the page hasn't shipped yet and there's no live URL to preserve.
OliviaShoup
requested changes
Aug 7, 2026
OliviaShoup
left a comment
OliviaShoup
left a comment
Contributor
There was a problem hiding this comment.
Hey, thank you for the PR! It looks really good. I've left some suggestions inline.
One note on scope: hugo/local/bin/py/preview_links.py is a build-script path fix unrelated to CCR-3653, so I haven't reviewed it. webops-platform is already a requested reviewer. Just flagging that this PR now spans two review domains and merging waits on both
Please let me know if you have any questions!
…ication prerequisites Normalize the safeguards table to consistent phrasing, fix the EBS snapshot optional/unconditional contradiction, restore the S3 Intelligent-Tiering reversibility fact alongside the preserved-rules fact, remove a duplicated safeguards sentence, switch remaining bold UI references to the ui shortcode, and add the required permission to the Notifications prerequisites.
Address Olivia's review comment: open the Overview with the page's own term and mention the UI tab once, then use plain "Automations" for the rest of the comparisons for consistency.
…n-notification-docs' into zeina.gebran/ccr-3653-remediation-notification-docs
The Cost Optimization Automation CRUD is backed by real Workflow Automation objects and is gated by the Workflows Write permission, not Cloud Cost Management Write.
Access to the Automations page requires Cloud Cost Management Write at the route level; creating or editing an automation additionally requires Workflows Write at the component level. These are two separate, both-required permissions, not either/or.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What does this PR do? What is the motivation?
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Drafted with Claude Code, based on the current merged Automations UI behavior (Remediation and Notification tabs).
Additional notes