adobe / adobe/aio-cli-plugin-runtime

Deployments do not update the existing triggers

Open
#335 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
21
Forks
33
PR merge metrics
No merged PRs in 30d

Description

**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

Contributor guide

Open the contributing guide

Research direction

Reproduce the interval change and trigger removal using the cron-jobs definition linked in the issue, checking state with `aio rt activations list` before and after deployment. Trace the deployment command's trigger handling; done means changed triggers use the new interval and removed triggers no longer run after deployment.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
43/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.