Open duynguyen opened 3 years ago
Thanks for raising this up @duynguyen ! Do you know if the configuration might be cached by the alarm package and hence would need to be refreshed somewhere else?
@meryllblanchet , yes that's possible. We might need some inspection in the alarms provider at Runtime level.
This only affects the "alarms related params", e.g. minutes
for /whisk.system/alarms/interval
, or cron
for /whisk.system/alarms/alarm
. Other params are updated properly with aio rt trigger update
command as well as aio app deploy
after manifest change.
Thanks for the update @duynguyen . Can you reproduce it using wsk CLI
?
this does works with the wsk CLI
In the manifest.yml file, you can specify schedule cron jobs with trigger feeds and rules.
After that you might want to update the interval to be 3 minutes instead of 1. Then
aio app deploy
. After redeployed you can check the info ofsync-users
trigger. It shows 3 minutes correctly.However the trigger is still fired every minute, like it was never updated.
This could be an issue with the alarms package itself, but creating this ticket for triaging purpose.