Has selectively disabling datapusher for datasets been considered?
- Dominant language
- Python
- Stars
- 82
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
We have a hypothetical (at this stage) requirement to disable the automatic datapusher for selected datasets (hosted externally to CKAN, frequently updated).
Has anybody experimented with, or discussed adding an option to the datapusher to ignore a resource?
Happy to hear thoughts, ideas, comments etc...
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing how the service identifies CKAN resources for automatic DataStore pushing, then determine where a per-resource exclusion option would need to be configured and enforced. Done would require an agreed scope, configuration behavior, and tests for selected resources being ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100