Question: Why does Zappa call unschedule/schedule when calling update?

[suriya]

I see that zappa update invokes self.schedule()

Zappa/zappa/cli.py

Line 1232 in bb5834f

self.schedule()

which in turn invokes self.zappa.schedule_events()

Zappa/zappa/cli.py

Line 1429 in bb5834f

self.zappa.schedule_events(

which calls self.unschedule_events

Zappa/zappa/core.py

Line 3002 in bb5834f

self.unschedule_events(

It looks like that on every update, Zappa unschedules all event handlers, removes permissions and creates them again.

Could someone explain the reasoning behind this implementation choice?

Specifically, if I comment out the call to schedule() while doing an update, would there be any negative consequence? I prefer to explicitly control events with schedule and unschedule.

[faiyeah]

I guess this is a trick to make sure all periodic scheduled event ( rate xxxxxxx) are run once immediately.

[monkut]

I believe that currently there no way to detect a change in the schedule, so the schedule is re-created on each deployment.

closing.