adobe / adobe/aio-cli-plugin-runtime
Deployments do not update the existing triggers
- 主要语言
- JavaScript
- 星标
- 21
- 派生
- 33
- PR 合并指标
- 30 天内没有已合并 PR
描述
**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
贡献指南
调研方向
使用 issue 中链接的 cron-jobs 定义重现间隔变更和触发器移除,并在部署前后使用 `aio rt activations list` 检查状态。跟踪部署命令对触发器的处理;完成的标准是已变更的触发器使用新的间隔,已移除的触发器在部署后不再运行。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript
- 领域
- cli, cloud
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 43/100