Parametrizable Event Gather CRON and Default Timedelta

Council Data Project v3.2.1

Council Data Project is a backend, frontend, and cookiecutter deployment for creating a whole database, storage system, and website, for archiving, exploring, and tracking municipal council action.

This library, cookiecutter-cdp-deployment is a cookiecutter template to deploy a whole new CDP infrastructure.

There are no new library changes from cdp-backend or cdp-frontend this release. This is a release that simply adds new parameters to the cookiecutter to make it easier to randomize CRON event gather schedules (via deployment bot), or provide a specific CRON from cookiecutter CLI, as well as set the default event gather timedelta lookback (how many days are checked for events each time the pipeline runs).

Those changes mean that the template also needed to be updated to utilize the new infrastructure deployment strategy.

⚠️ ⚠️

This release is a "breaking" change for instances.

Instance maintainers will want to do the following:

• Add a value to the .cookiecutter.yaml file called: event_gather_timedelta_lookback_days with an integer value for the number of days to check during the event gather. The default (and current value prior to this update to make it parametrizable) is 2 for two days. To decide what this parameter should be, a general rule of thumb is: "how long does it take for the municipality to post events"
• Add a value to the .cookiecutter.yaml file called: event_gather_cron with a CRON string for how often to run the event gather pipeline. The default (and current value prior to this update to make it parametrizable) is "26 0,6,12,18 * * *". Which means: "run the pipeline at 12:26am, 6:26am, 12:26pm and 6:26pm UTC everyday". A general rule of thumb is: "if the event gather timedelta is large, the pipeline doesn't need to run as often."
• Run just update-from-cookiecutter or make update-from-cookiecutter

⚠️ ⚠️

Full Changelog: v3.2.0...v3.2.1