Add columns to `worker_oauth` to track last key rotation date and key expiry date

Abierto
#573 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
53/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
database

Línea de trabajo

Start by locating the worker_oauth table definition and the code that creates or updates its keys. Check how schema changes and database migrations are handled in the project. Done means the table can store the last rotation date and a nullable expiry date, while existing key records continue to work.

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

Descripción

database security

the worker_oauth table (which is used for storing keys on instances where there are more than one of them) should ideally have columns to track key dates related to the keys, such as:

  • When they were last rotated (this can probably also account for when they were added/last updated too)
  • When they expire (nullable, some platforms allow no expiry, and some may mandate that theres an expiry date)
    - When they were first added (dubiously useful and hard to retroactively add as a mandatory field)

Having these dates would be useful to display in the UI (as part of #55) and might be helpful for reminding instance owners if some of their keys are up for expiry soon (or if they want a reminder to rotate them periodically)

Currently, if this information is desired to be stored, it can be shoved into the name field (using it more like a comments field)

Lenguaje dominante
Python
Estrellas
17
Forks
30
Merge medio
6 h 16 min
PR fusionados (30 d)
9

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 chaoss/CollectOSS

Todos los issues de chaoss/CollectOSS

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.