Skip to content

SLEAK-5570: support scope page - #222

Merged
mjroson merged 3 commits into
developfrom
feat/SLEAK-5570-support-scope
Jul 22, 2026
Merged

SLEAK-5570: support scope page#222
mjroson merged 3 commits into
developfrom
feat/SLEAK-5570-support-scope

Conversation

@agustinoli

@agustinoli agustinoli commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

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).

  • Qué cubre el soporte: consultas sobre la plataforma, errores de infraestructura levantada por SleakOps, soporte en actualización de recursos.
  • Qué queda fuera del alcance estándar.
  • Tabla de responsabilidades completa (lado SleakOps / lado cliente).
  • Cómo abrir un ticket y qué esperar del flujo.

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

  • El cross-link a cost-review-guide (SLEAK-6054, PR SLEAK-6054: cost review tutorial #219) se agrega cuando ambas ramas estén mergeadas a develop.
  • Build de Docusaurus verificado localmente.

Summary by CodeRabbit

  • Documentación
    • Añadida la guía de Soporte en español e inglés, con información sobre cómo solicitar ayuda, problemas cubiertos y recursos recomendados.
    • Incluida una sección para aclarar responsabilidades entre SleakOps y el usuario sobre plataforma, aplicaciones, datos y copias de seguridad.
    • Actualizado el Modelo de Responsabilidad Compartida con enlaces externos más claros y una referencia directa a la documentación de soporte.

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.
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@agustinoli, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ebdbc6a2-613d-430e-b250-c38ec9bdcb14

📥 Commits

Reviewing files that changed from the base of the PR and between b94da24 and 487a311.

📒 Files selected for processing (2)
  • content/docs/en/support.mdx
  • content/docs/es/support.mdx

Walkthrough

Se 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.

Changes

Documentación de soporte

Layer / File(s) Summary
Páginas de soporte bilingües
content/docs/en/support.mdx, content/docs/es/support.mdx
Se incorporan páginas de soporte con navegación, tipos de consultas cubiertas, recursos recomendados, tabla de responsabilidades y orientación para casos inciertos.
Enlaces desde los modelos de responsabilidad
content/docs/en/responsability-model.mdx, content/docs/es/responsability-model.mdx
Se ajusta el enlace al modelo de responsabilidad compartida de AWS, se añade el icono externo y se enlaza con Support.

Estimated code review effort: 2 (Simple) | ~10 minutes

Poem

Documentos que dan dirección,
soporte en cada idioma,
AWS con su enlace brillante,
responsabilidades en fila,
y conflictos resueltos a las piñas.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed El título resume correctamente la incorporación de la página de alcance de soporte.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/SLEAK-5570-support-scope

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6d5c9b2 and b94da24.

📒 Files selected for processing (4)
  • content/docs/en/responsability-model.mdx
  • content/docs/en/support.mdx
  • content/docs/es/responsability-model.mdx
  • content/docs/es/support.mdx

Comment thread content/docs/en/support.mdx Outdated

Si tienes un problema o una pregunta, la forma más rápida de obtener ayuda es a través de **Support**, en la barra lateral principal de la consola — combina un chat con IA y tickets de soporte para tu cuenta. Antes de escribir, vale la pena buscar aquí en la documentación: la mayoría de las preguntas del día a día ya están respondidas en un tutorial o FAQ.

## Qué cubre nuestro soporte

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Que cubre nuestro soporte:

  • Errores propios de la plataforma
  • Errores de recursos de infraestructura manejados automaticamente por SleakOps
  • Soporte en actualizacion de recursos levantados con Sleakops
  • Bloqueos de estado de infraestructura
  • Soporte a workarround de customizaciones que no cubre la plataforma.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Aplicado en 487a311 — la sección «Qué cubre nuestro soporte» / «What our support covers» ahora lista los cinco ítems (EN/ES), con un pulido menor de redacción: errores propios de la plataforma, errores en recursos de infraestructura gestionados automáticamente por SleakOps, ayuda para actualizar recursos provisionados con SleakOps, bloqueos de estado de la infraestructura, y acompañamiento con workarounds para customizaciones que la plataforma no cubre.

…fix (SLEAK-5570)

- Replace the "What our support covers" list with the canonical five
  items (platform errors, managed-resource errors, resource updates,
  state locks, customization workarounds), in EN and ES.
- "Data & backups" row: backup and restoration policies for managed
  dependencies (RDS, S3, RabbitMQ) are owned by the client, aligned
  with the Responsibility Model.
@mjroson
mjroson merged commit 17269d7 into develop Jul 22, 2026
1 check passed
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.

3 participants