Start indexing after deployment

[kesara]

Description

At the moment, after a deployment, each data-set indexer has to be kick-started.
This can be improved by adding a step to start indexing for each data-set after deployment.

Code of Conduct

• I agree to follow the IETF's Code of Conduct

[microamp]

[2024-08-21 02:30:31,302: INFO/Beat] beat: Starting...
[2024-08-21 02:30:34,196: INFO/MainProcess] Connected to redis://localhost:6379//
...
[2024-08-21 02:30:34,199: INFO/MainProcess] mingle: searching for neighbors
[2024-08-21 02:30:35,208: INFO/MainProcess] mingle: all alone
[2024-08-21 02:30:35,218: INFO/MainProcess] celery@bib-bibxml-5c6746647-bntsf ready.
...
[2024-08-21 04:00:31,464: INFO/Beat] Scheduler: Sending due task index-misc (sources.tasks.fetch_and_index_task)
[2024-08-21 04:00:31,469: INFO/Beat] Scheduler: Sending due task index-rfcs (sources.tasks.fetch_and_index_task)
[2024-08-21 04:00:31,469: INFO/MainProcess] Task sources.tasks.fetch_and_index_task[9ce89346-9d34-409b-a8ed-6d05c1ab2563] received
[2024-08-21 04:00:31,472: INFO/MainProcess] Task sources.tasks.fetch_and_index_task[14c4206a-f432-4e4d-8fac-6e61443653d1] received
[2024-08-21 04:00:31,472: INFO/Beat] Scheduler: Sending due task index-nist (sources.tasks.fetch_and_index_task)
[2024-08-21 04:00:31,474: INFO/Beat] Scheduler: Sending due task index-3gpp (sources.tasks.fetch_and_index_task)
[2024-08-21 04:00:31,475: INFO/MainProcess] Task sources.tasks.fetch_and_index_task[68596175-8cc7-4ae1-b1af-fe137695972a] received
[2024-08-21 04:00:31,476: INFO/MainProcess] Task sources.tasks.fetch_and_index_task[92bd43cb-4cb1-40cf-add9-7dc4d1991d56] received
...

suggests that the tasks were triggered approx 90 minutes [1] after the celery container started, meaning no manual trigger was necessary.

1. AUTO_REINDEX_INTERVAL currently set to 5400 seconds (= 90 mins)