adobe / adobe/aio-cli-plugin-runtime

Deployments do not update the existing triggers

Abierto
#335 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
JavaScript
Estrellas
21
Forks
33
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**Describe the bug**

When I introduced a trigger with 1 minute interval, it worked fine. However, changing the interval from 1 minute to 5 minutes was not reflected. Additionally, removing the trigger in my code did not cause any removal on runtime.

**To Reproduce**
Steps to reproduce the behavior:
1. Define a trigger as described here https://developer.adobe.com/app-builder/docs/resources/cron-jobs/lesson2/
2. Execute `aio rt activations list` and make sure that the corresponding action is triggered every minute.
3. Change your trigger definition interval from 1 to 5 and deploy the app.
4. Execute `aio rt activations list` and observe that the corresponding action is still triggered every minute.

**Expected behavior**
After changing the mentioned sample trigger definition interval from 1 to 5, execute `aio rt activations list` should display that the corresponding action is triggered every 5 minutes.
What I expect in general, is that any deployable procedure, definition must override the existing app. In this particular example, I would propose listing all available triggers and deleting them prior to a deployment.

**Screenshots**
N/A

**Desktop (please complete the following information):**
- OS: MacOS
- Browser : Chrome
- Version : Latest

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Reproduce el cambio de intervalo y la eliminación del trigger usando la definición de cron-jobs enlazada en el issue, comprobando el estado con `aio rt activations list` antes y después del despliegue. Rastrea el manejo de triggers del comando de despliegue; se considera terminado cuando los triggers modificados usan el nuevo intervalo y los triggers eliminados ya no se ejecutan después del despliegue.

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

Evaluación

Stack tecnológico
javascript
Área
cli, cloud
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
43/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.