feat: show EventBridge Scheduler schedules in the EventBridge view

Abierto
#147 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, rust
Área
cli, cloud

Línea de trabajo

Start by reading docs/recipes/README.md and the EventBridge view PR, then wait for blocker #146 to merge. Add AWS Scheduler schedule fetching and rows with working pivots, including the disabled-schedule rule; update tests, docs, and the changeset. Run the listed formatting, clippy, and test commands; done means they pass and the view shows schedules.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

size: S

Why

The roxtarget daily digest runs on EventBridge Scheduler, which is a separate API from rules. Showing schedules next to rules keeps all timers in one place.

Steps

  1. New crate aws-sdk-scheduler. Fetch list_schedules.
  2. Add a kind column (rule or schedule) to the EventBridge view and add schedules as rows. Decide in the PR whether that is one model with a kind field or an enum; either is fine, explain the choice.
  3. Console for a schedule: https://console.aws.amazon.com/scheduler/home?region=<region>#schedules/<group>/<name>. CLI: aws scheduler get-schedule --name <name> --group-name <group> --region <region>.
  4. A disabled schedule should also trigger eventbridge_rule_disabled, or a sibling rule. Test it.

Where to look

  • the EventBridge view PR

Done when

  • Schedules appear as rows with working pivots
  • Tests
  • Docs and changeset
  • cargo fmt --all, cargo clippy --all-targets -- -D warnings, and cargo test --all pass, with output pasted in the PR

Check against AWS

Optional. Unit tests are enough for this issue.

Blocked by

#146. Start this after that is merged.

Size: S. Read docs/recipes/README.md before starting.

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
4 h 8 min
PR fusionados (30 d)
8

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fells-code/seamless-glance

Todos los issues de fells-code/seamless-glance

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.