Feature Description
On a classical GeoNode deployment with Docker, the solution to synchronize GeoNode with GeoServer configuration after for example a mass upload of new data in Geoserver is to use the GeoNode management CLI to trigger the synchronization.
On K8s, it is not a good practice to do so. It would be better to have a regular call to the management CLI to check if a sync must be done.
Proposed Solution
Add an optional cronjob which calls the management CLI for synchronizing GeoNode with GeoServer. The frequency should be configurable and the workspace/datastore filters of the command as well.
Additional Information
Any additional information or context that may be helpful in implementing the feature.
Feature Description
On a classical GeoNode deployment with Docker, the solution to synchronize GeoNode with GeoServer configuration after for example a mass upload of new data in Geoserver is to use the GeoNode management CLI to trigger the synchronization.
On K8s, it is not a good practice to do so. It would be better to have a regular call to the management CLI to check if a sync must be done.
Proposed Solution
Add an optional cronjob which calls the management CLI for synchronizing GeoNode with GeoServer. The frequency should be configurable and the workspace/datastore filters of the command as well.
Additional Information
Any additional information or context that may be helpful in implementing the feature.