docs: support-scope review adjustments + KMS step in RDS snapshot restore - #231
docs: support-scope review adjustments + KMS step in RDS snapshot restore#231agustinoli wants to merge 3 commits into
Conversation
…tore Support page (EN/ES): - "Something's wrong in your application" now points to the AI-powered Autodiagnostic as a first step. - "The application feels slow" links to Grafana instead of Kubecost/Prometheus. - Dockerfile/build questions link to "Configure your Dockerfile" instead of Chart Dependencies. - AWS spend bullet also links to the Cost Review Guide tutorial. - Responsibility table: SleakOps covers the resources it creates as long as they aren't modified directly in AWS; secure storage of data moves to the client side, next to backup/restoration policies. RDS snapshot migration tutorial (EN/ES): - Case 3 restore: new step to select the KMS key in the "Create an RDS from a snapshot" form when the snapshot isn't encrypted with the default AWS-managed key.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (3)
WalkthroughSe actualizan las páginas bilingües de responsabilidades y el procedimiento bilingüe para restaurar snapshots RDS cifradas con una clave KMS personalizada. ChangesResponsabilidades de soporte
Restauración de snapshots RDS
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
content/docs/en/support.mdx (1)
32-32: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winCorrige la redacción de la capacidad de CI/CD.
CI/CD pipelines capabilitiessuena antinatural y deja ambiguo el alcance de la responsabilidad. UsadCI/CD pipeline capabilitiesoCI/CD pipelinespara mantener la tabla clara y alineada con la versión española.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/docs/en/support.mdx` at line 32, Update the “Your application” row in the support responsibility table to replace “CI/CD pipelines capabilities” with the natural “CI/CD pipeline capabilities” wording, leaving the surrounding responsibility descriptions unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/docs/en/support.mdx`:
- Line 33: Update the “Data & backups” row in content/docs/en/support.mdx lines
33-33 to state that users configure and manage dependency backup and restoration
policies in AWS, removing any suggestion that SleakOps provides automated RDS
backups. Apply the same clarification in Spanish in content/docs/es/support.mdx
lines 33-33, explicitly avoiding attribution of RDS backup provision to
SleakOps.
In `@content/docs/es/support.mdx`:
- Line 25: Actualiza el enlace de AWS en el contenido de soporte en español para
que apunte a https://docs.aws.amazon.com, alineándolo con la versión inglesa y
manteniendo intacto el resto del texto.
---
Nitpick comments:
In `@content/docs/en/support.mdx`:
- Line 32: Update the “Your application” row in the support responsibility table
to replace “CI/CD pipelines capabilities” with the natural “CI/CD pipeline
capabilities” wording, leaving the surrounding responsibility descriptions
unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 49030514-7f6f-4695-962f-4b82598f9a5d
📒 Files selected for processing (4)
content/docs/en/support.mdxcontent/docs/es/support.mdxcontent/tutorials/en/migrate-rds-snapshot-between-accounts.mdxcontent/tutorials/es/migrate-rds-snapshot-between-accounts.mdx
The RDS dependency schema validates kmsKeyId against a full-ARN pattern, so the restore step now says to enter the key's full ARN instead of "selecting" it.
- "Data & backups" SleakOps cell now says the platform exposes the resource's backup settings in the dependency form (RDS "Automated Backup" toggle, retention period) instead of "provides backup options", removing the reading that SleakOps runs the backups. - ES: AWS documentation link points to docs.aws.amazon.com like the English version, instead of the aws.amazon.com homepage.
Ajustes acordados en la reunión de revisión de la página de soporte, más un paso faltante en el tutorial de migración de snapshots de RDS. Todo en EN y ES.
Página de soporte (
content/docs/{en,es}/support.mdx)Sección "Dónde mirar primero":
Tabla "Responsabilidad de un vistazo":
Tutorial
migrate-rds-snapshot-between-accounts(content/tutorials/{en,es}/)kmsKeyId: "If not specified, the default AWS-managed key is used").Build de Docusaurus verificado en ambos idiomas.
Summary by CodeRabbit
Documentación
Tutoriales