Quickly filter REST API for disabled stores / resources
Description
You can use the REST API to determine layer status:
And check for <enabled>false</enabled> one at a time.
Using this approach it is labor intensive to scan through available layers and detect those which are unavailable. Improvement would be to add an parameter enabled=true or enabled=false filter when listing stores or resources.
/workspaces/<ws>/datastores.json?enabled=false
Since Feature types already provide several parameters it is a bit more tricky to think of sensible addition:
/workspaces/<ws>/datastores/<ds>/featuretypes.json?enabled=false - only feature types which are configured but are distabled are returned
Environment
None
Activity
Andrea Aime
April 25, 2018 at 1:43 PM
Closing all feature/improvement requests that have seen no changes in one year.
This does not mean the request was not valid, we just recognize it failed to gather developer resources for a long time.
Medium
You can use the REST API to determine layer status:
And check for
<enabled>false</enabled>one at a time.Using this approach it is labor intensive to scan through available layers and detect those which are unavailable.
Improvement would be to add an parameter
enabled=trueorenabled=falsefilter when listing stores or resources./workspaces/<ws>/datastores.json?enabled=falseSince Feature types already provide several parameters it is a bit more tricky to think of sensible addition:
/workspaces/<ws>/datastores/<ds>/featuretypes.json?enabled=false- only feature types which are configured but are distabled are returned