SLEAK-5570: support scope page#222
Open
agustinoli wants to merge 2 commits into
Open
Conversation
Add a client-facing Support page defining what SleakOps support covers, with self-service pointers for common out-of-scope questions and a short responsibility summary. Cross-link it from the existing Shared Responsibility Model page.
WalkthroughSe añaden páginas de soporte en inglés y español con información sobre cobertura, responsabilidades y recursos iniciales. Los modelos de responsabilidad actualizan el enlace de AWS y enlazan con la nueva documentación de soporte. ChangesDocumentación de soporte
Estimated code review effort: 2 (Simple) | ~10 minutes 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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`:
- Around line 29-31: Update the “Data & backups” row in both
content/docs/en/support.mdx (lines 29-31) and content/docs/es/support.mdx (lines
29-31) so it no longer attributes backup or restoration of customer-managed
dependencies to SleakOps; align the responsibility wording with the
Responsibility Model, stating that the client manages backups for dependencies
such as RDS, S3, and RabbitMQ.
🪄 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
Run ID: 5d2c34eb-4a5b-4b30-bc37-479f24382c20
📒 Files selected for processing (4)
content/docs/en/responsability-model.mdxcontent/docs/en/support.mdxcontent/docs/es/responsability-model.mdxcontent/docs/es/support.mdx
Comment on lines
+29
to
+31
| | **Platform & infrastructure** | Clusters, networking, provisioning, and the resources SleakOps creates for you | Configure environment variables, define resource requirements, and monitor usage | | ||
| | **Your application** | Provide runtime environment, CI/CD pipelines capabilities, and observability tools (logs/metrics) | Your code, its dependencies, and its performance | | ||
| | **Data & backups** | Automated execution, secure storage, and restoration capabilities. | Backup policies for your dependencies (see [Responsibility Model](/docs/responsability-model)) | |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== support.mdx (en) ==\n'
sed -n '1,120p' content/docs/en/support.mdx
printf '\n== support.mdx (es) ==\n'
sed -n '1,120p' content/docs/es/support.mdx
printf '\n== responsibility model references ==\n'
rg -n "backup|restore|restoration|RDS|S3|RabbitMQ|dependenc" content/docs -SRepository: sleakops/docs
Length of output: 50370
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf '\n== responsibility model (en) ==\n'
cat -n content/docs/en/responsability-model.mdx | sed -n '1,120p'
printf '\n== backup-related mentions in support + responsibility ==\n'
rg -n "backup|restoration|restore|dependencies \(RDS, S3, RabbitMQ|don't support backups|not support backups" content/docs/en/support.mdx content/docs/en/responsability-model.mdx -SRepository: sleakops/docs
Length of output: 1664
Ajustad la fila de “Data & backups” en ambas versiones
Ahora mismo la tabla le atribuye a SleakOps “restoration capabilities”, pero el modelo de responsabilidad dice que los backups de las dependencias (RDS, S3, RabbitMQ, etc.) los gestiona el cliente. Alinead ese texto para que no se contradigan.
📍 Affects 2 files
content/docs/en/support.mdx#L29-L31(this comment)content/docs/es/support.mdx#L29-L31
🤖 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` around lines 29 - 31, Update the “Data &
backups” row in both content/docs/en/support.mdx (lines 29-31) and
content/docs/es/support.mdx (lines 29-31) so it no longer attributes backup or
restoration of customer-managed dependencies to SleakOps; align the
responsibility wording with the Responsibility Model, stating that the client
manages backups for dependencies such as RDS, S3, and RabbitMQ.
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
1 participant
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.
Resumen
Agrega la página pública de alcance de soporte (
content/docs/{en,es}/support.mdx), que documenta cómo usar el soporte de SleakOps y qué cubre el plan estándar, cross-linkeada con el modelo de responsabilidad (responsability-model.mdx).Antes de esta página no existía ninguna referencia pública de soporte/alcance en docs — el punto más cercano era
responsability-model.mdx(solo backups de AWS).Jira
SLEAK-5570
Notas
cost-review-guide(SLEAK-6054, PR SLEAK-6054: cost review tutorial #219) se agrega cuando ambas ramas estén mergeadas adevelop.Summary by CodeRabbit