Check datastore_active on resource update

[ThrawnCA]

The datastore_active flag can sometimes get out of sync with the actual state of the datastore, eg due to race conditions like ckan/ckan#4663

It should be relatively cheap to add an "after update" step to ensure that the flag matches the datastore state.

[wardi]

👍 how about a cli command to update datastore_active for all/some resources as well?

[ThrawnCA]

That would be possible... Although perhaps a more general solution would be better. This isn't the first time I've seen a situation where it would be helpful to essentially "bump" a resource/dataset and apply the latest after_update hooks from all extensions. Perhaps a command could be added to the core to apply a package_patch or resource_patch to all or selected objects.

[wardi]

That's a good idea. was actually thinking of adding an action to core to reindex a dataset. Maybe things like checking datastore_active, updating tracking counts etc. could be hooked to that action.

[ThrawnCA]

A CLI command to bump the state of a dataset could be raised as a separate issue, but the original purpose of this one is complete.